 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| cyrf69103 programmable radio on chip low power cypress semiconductor corporation ? 198 champion court ? san jose , ca 95134-1709 ? 408-943-2600 document number: 001-07611 rev *i revised february 25, 2013 programmable radio on chip low power proc? lp features single device, two functions ? 8-bit flash based mcu function and 2.4 ghz radio transceiver function in a single device. flash based microcontroller function ? m8c based 8-bit cpu, optimized for human interface devices (hid) applications ? 256 bytes of sram ? 8 kbytes of flash memory with eeprom emulation ? in-system reprogrammable ? cpu speed up to 12 mhz ? 16-bit free running timer ? low power wakeup timer ? 12-bit programmable interval timer with interrupts ? watchdog timer industry leading 2.4 ghz radio transceiver function ? operates in the unlicensed worl dwide industrial, scientific, and medical (ism) band (2.4 ghz to 2.483 ghz) ? dsss data rates of up to 250 kbps ? gfsk data rate of 1 mbps ? ?97 dbm receive sensitivity ? programmable output power up to +4 dbm ? auto transaction sequencer (ats) ? framing crc and auto ack ? received signal strength indication (rssi) ? automatic gain control (agc) component reduction ? integrated 1.8 v boost converter ? gpios that require no external components ? operates off a single crystal flexible i/o ? 2 ma source current on all gpio pins. configurable 8 ma or 50 ma/pin current sink on designated pins ? each gpio pin supports high impedance inputs, configurable pull up, open drain output, cmos/ttl inputs, and cmos output ? maskable interrupts on all i/o pins operating voltage from 1.8 v to 3.6 v dc operating temperature from 0 to 70 c pb-free 40-pin qfn package advanced development tools based on cypress?s psoc ? tools logic block diagram microcontroller function radio function rfn rfp rfbias xtal 12 mhz v reg v bat0 resv vdd 470 nf p0_1,3,4,7 p1_0:2,6:7 p2_0:1 470nf gnd . . . . . . . irq/gpio miso/gpio xout/gpio pactl/gpio gnd v cc v dd_micro p1.5/mosi p1.4/sck p1.3/nss rst mosi sck nss v bat1 v bat2 v cc1 v cc2 v cc3 v io gnd . . . . . 2 5 4 l/d 10 f 47f v cc
cyrf69103 document number: 001-07611 rev *i page 2 of 72 contents applications ...................................................................... 3 functional description ..................................................... 3 functional overview ........................................................ 3 2.4 ghz radio function .............................................. 3 data transmission modes ........................................... 3 microcontroller function .............................................. 3 backward compatibility .......... .............. .............. ......... 4 ddr mode ................................................................... 4 sdr mode .................................................................. 5 pinouts .............................................................................. 6 pin definitions .................................................................. 6 functional block overview .............................................. 7 2.4 ghz radio ............................................................. 7 frequency synthesizer ................................................ 7 baseband and framer ................................................. 7 packet buffers and radio configuration registers ..... 8 auto transaction sequencer (ats) ............................ 8 interrupts ..................................................................... 9 clocks ............ .............. .............. .............. ........... ......... 9 gpio interface ............................................................ 9 power on reset/low voltage detect .......................... 9 timers ......................................................................... 9 power management ............... .............. .............. ......... 9 low noise amplifier (lna) and received signal strength indi cation (rssi) ..................... 11 receive spurious response .. ................................... 11 spi interface .................................................................... 11 3-wire spi interface .................................................. 11 4-wire spi interface .................................................. 11 spi communication and transact ions .......... ............ 12 spi i/o voltage references ...................................... 12 spi connects to external devi ces ....... .............. ....... 12 cpu architecture ............................................................ 13 cpu registers ................................................................. 14 flags register ........................................................... 14 accumulator register .......... ...................................... 14 index register ........................................................... 15 stack pointer register ......... ...................................... 15 cpu program counter high register ....................... 15 cpu program counter low register ........................ 15 addressing modes ......................................................... 16 source immediate ..................................................... 16 source direct ............................................................. 16 source indexed ................... ...................................... 16 destination direct ...................................................... 16 destination indexed ................................................... 17 destination direct source immediate ........................ 17 destination indexed source immediate .................... 17 destination direct source direct ............................... 17 source indirect post incremen t ................................. 18 destination indirect post increment .......................... 18 instruction set summary ............................................... 19 memory organization ..................................................... 20 flash program memory organization ....................... 20 data memory organization ....................................... 21 flash .......................................................................... 21 srom ........................................................................ 21 srom function descriptions .................................... 22 clocking .......................................................................... 25 srom table read description ................................. 26 clock architecture description .................................. 27 cpu clock during sleep mode ................................. 31 reset .......... .............. .............. ........... ............ ........... ........ 32 power on reset ........................................................ 33 watchdog timer reset .............................................. 33 sleep mode ...................................................................... 33 sleep sequence ........ .............. ............... ........... ........ 33 low power in sleep mode ......................................... 34 wakeup sequence .................................................... 34 low voltage detect control ........................................... 36 por compare state ................................................. 37 eco trim register .................................................... 37 general purpose i/o ports ............................................. 38 port data registers ................................................... 38 gpio port configuration ........................................... 39 gpio configurations for low power mode ............... 44 serial peripheral interface (s pi) ................................ 45 spi data register ...................................................... 46 spi configure register .............................................. 46 spi interface pins ...................................................... 48 timer registers .............................................................. 48 registers ................................................................... 48 interrupt controller ......................................................... 51 architectural description ........................................... 51 interrupt processing .................................................. 52 interrupt latency ....................................................... 52 interrupt registers .............. ....................................... 52 microcontroller function register summary ............. 56 radio function register summary ............................... 58 absolute maximum ratings .......................................... 59 dc characteristics ......................................................... 59 ac characteristics ......................................................... 61 rf characteristics .......................................................... 65 ordering information ...................................................... 67 ordering code definitions ..... .................................... 67 package handling ........................................................... 68 package diagram ............................................................ 68 acronyms ........................................................................ 70 document conventions ................................................. 70 units of measure ....................................................... 70 document history page ................................................. 71 sales, solutions, and legal information ...................... 72 worldwide sales and design s upport ......... .............. 72 products .................................................................... 72 psoc solutions ......................................................... 72 cyrf69103 document number: 001-07611 rev *i page 3 of 72 applications the cyrf69103 proc lp is targeted for the following applications: wireless hid devices: ? mice ? remote controls ? presenter tools ? barcode scanners ? pos terminal general purpose wireless applications: ? industrial applications ? home automation ? white goods ? consumer electronics ? to y s functional description proc lp devices are integrated radio and microcontroller functions in the same package to provide a dual-role single-chip solution. communication between the micr ocontroller and the radio is through the radio?s spi interface. functional overview the cyrf69103 is a complete radio system-on-chip device, providing a complete rf system solution with a single device and a few discrete components. the cyrf69103 is designed to implement low cost wireless systems operating in the worldwide 2.4 ghz industrial, scientific, and medical (ism) frequency band (2.400 ghz to 2.4835 ghz). 2.4 ghz radio function the soc contains a 2.4 ghz 1 mbps gfsk radio transceiver, packet data buffering, packet fr amer, dsss baseband controller, received signal strength indication (rssi), and spi interface for data transfer and device configuration. the radio supports 98 discrete 1 mhz channels (regulations may limit the use of some of these channels in certain jurisdictions). in dsss modes the baseband performs dsss spreading/despreading, while in gfsk mode (1 mb/s - gfsk) the baseband performs start of frame (sof), end of frame (eof) detection, and crc16 generation and checking. the baseband may also be configur ed to automatically transmit acknowledge (ack) handshake packets whenever a valid packet is received. when in receive mode, with packet framing enabled, the device is always ready to receive data transmitted at any of the supported bit rates, except s dr, enabling the implementation of mixed-rate systems in which different devices use different data rates. this also enables the implementation of dynamic data rate systems, which use high data ra tes at shorter distances and/or in a low moderate interference environment, and change to lower data rates at longer distances and/or in high interference environments. the radio meets the following worldwide regulatory requirements: europe: ? etsi en 301 489-1 v1.4.1 ? etsi en 300 328-1 v1.3.1 north america: ? fcc cfr 47 part 15 japan: ? arib std-t66 data transmission modes the radio supports four different data transmission modes: in gfsk mode, data is transmitted at 1 mbps, without any dsss in 8dr mode, 1 byte is encoded in each pn code symbol transmitted in ddr mode, 2 bits are encoded in each pn code symbol transmitted in sdr mode, a single bit is encoded in each pn code symbol transmitted both 64-chip and 32-chip data pn codes are supported. the four data transmission modes apply to the data after the start of packet (sop). in particular, the packet length, data and crc are all sent in the same mode. microcontroller function the mcu function is an 8-bit flash-programmable microcontroller. the instruction set is optimized specifically for hid and a variety of other embedded applications. the mcu function has up to 8 kbytes of flash for user?s code and up to 256 bytes of ram for stack space and user variables. in addition, the mcu function includes a watchdog timer, a vectored interrupt controller, a 16-bit free running timer, and 12-bit programmable interrupt timer. the microcontroller has 15 gpio pins grouped into multiple ports. with the exception of the four radio function gpios, each gpio port supports high impedance inputs, configurable pull up, open drain output, cmos/ttl inputs and cmos output. up to two pins support programmable drive strength of up to 50 ma. additionally, each i/o pin can be used to generate a gpio interrupt to the microcontroller. each gpio port has its own gpio interrupt vector with the exceptio n of gpio port 0. gpio port 0 has two dedicated pins that have independent interrupt vectors (p0.3?p0.4). the microcontroller features an internal oscillator. the proc lp includes a watchdog timer, a vectored interrupt controller, a 12-bit programmable interval timer with configurable 1 ms interrupt and a 16-b it free running timer. in addition, the cyrf69103 ic has a power management unit (pmu), which enables direct connection of the device to any battery voltage in the range 1.8 v to 3.6 v. the pmu conditions the battery voltage to provide the supply voltages required by the device and may supply external devices. cyrf69103 document number: 001-07611 rev *i page 4 of 72 backward compatibility the cyrf69103 ic is fully interoperable with the main modes of the first generation cypress radios namely the cywusb6934 -ls and cywwusb6935-lr devices. the 62.5 kbps mode is supported by selecting 32 chip ddr mode. similarly, the 15.675 kbps mode is supported by selecting 64 chip sdr mode in this method, a suitably configured cyrf69103 ic device may transmit data to or receive data from a first generation device, or both. backwards compatibility requires disabling the sop, length, and crc16 fields. this section provides the different configurations of the registers and firmware that enable a new generation radio to communicate with a first generation radio. there are two possible modes: sdr and ddr mode (8-dr and gfsk modes are not present in the first generation radio). the se cond generation radio must be initialized using the radioinitapi of the lp radio driver and then the following registers? bits need to be configured to the given byte values. essentially, the following deactivates the added features of the second generation radio and takes it down to the level of the first generation radio. the data format, data rates, and the pn codes used are recogni zable by the first generation radio. ddr mode table 1. ddr mode register value description tx_cfg_adr 0x16 32 chip pn code, ddr, pa = 6 rx_cfg_adr 0x4b agc is enabled. lna and attenuator are disabled. fast turnaround is disabled, the device uses high side receive injection and hi-lo is disabled. overwrite to receive buffer is enabled and the rx buffer is configured to receive eight bytes maximum. xact_cfg_adr 0x05 autoack is disabled. forcing end stat e is disabled. the device is configured to transition to idle mode after a receive or tran smit. ack timeout is set to 128 s. framing_cfg_adr 0x00 all sop and framing features ar e disabled. disable len_en = 0 if eop is needed. tx_override_adr 0x04 disable transmit crc-16. rx_override_adr 0x14 the receiver rejects packets with a zero seed. the rx crc-16 checker is disabled and the receiver accepts bad packets that do not match the seed in crc_seed registers. this helps in communication with the first generation radio that does not have crc capabilities. analog_ctrl_adr 0x01 set all slow. when set, the synthesizer settle time for all channels is the same as the slow channels in the first generation radio. data32_thold_adr 0x03 sets the number of allowed corrupted bits to 3. eop_ctrl_adr 0x01 sets the number of consecutive symbols for non-corre lation to detect end of packet. preamble_adr 0xaaaa05 aaaa are the two preamble bytes. an y other byte can also be written into the preamble register file. recommended counts of the preamble bytes to be sent must be >4. cyrf69103 document number: 001-07611 rev *i page 5 of 72 sdr mode table 2. sdr mode register value description tx_cfg_adr 0x3e 64 chip pn code, sdr mode, pa = 6 rx_cfg_adr 0x4b agc is enabled. lna and attenuator are disabled. fast turnaround is disabled, the device uses high side receive injection and hi-lo is disabled. overwrite to receive buffer is enabled and rx buffer is configured to receive eight bytes maximum. enables rxow to allow new packets to be loaded into the receive buffer. this also enables the valid bit which is used by the first generation radio?s error correction firmware. xact_cfg_adr 0x05 autoack is disabled. forcing end stat e is disabled. the device is configured to transition to idle mode after receive or tran smit. ack timeout is set to 128 s. framing_cfg_adr 0x00 all sop and framing features are disabled. disable len_en=0 if eop is needed. tx_override_adr 0x04 disable transmit crc-16. rx_override_adr 0x14 the receiver rejects packets with a zero seed. the rx crc-16 checker is disabled and the receiver accepts bad packets that do not match the seed in the crc_seed registers. this helps in communication with the firs t generation radio that does not have crc capabilities. analog_ctrl_adr 0x01 set all slow. when set, the synthesizer settle time for all channels is the same as the slow channels in the first generation radio, for manual ack consistency data64_thold_adr 0x07 sets the number of allowed corrup ted bits to 7 which is close to the recommended 12% value. eop_ctrl_adr 0xa1 sets the number of consecutive symbols for non-corre lation to detect end of packet. preamble_adr 0xaaaa09 aaaa are the two preamble bytes. an y other byte can also be written into the preamble register file. recommended counts of the preamble bytes to be sent must be >8. cyrf69103 document number: 001-07611 rev *i page 6 of 72 pinouts figure 1. pin diagram rf bias v bat2 xtal p2.1 v cc v bat1 p0.4 v cc p0.1 p0.3 v reg p0.7 p1.6 v bat0 l/d p1.7 pactl / gpio v io v dd_1.8 rst rf n nc p2.0 v cc nc nc resv nc gnd rf p v dd_micro p1.3 / ss p1.4 / sck irq / gpio p1.5 / mosi miso / gpio xout / gpio p1.2 p1.1 p1.0 * e-pad bottom side 21 22 23 24 25 26 27 28 29 30 11 12 13 14 15 16 17 18 19 20 10 9 8 7 6 5 4 3 2 40 39 38 37 36 35 34 33 32 31 1 cyrf69103 proc lp corner tabs pin definitions pin name description 1 p0.4 individually configured gpio 2 xtal 12 mhz crystal 3, 7, 16 v cc 2.4 v to 3.6 v supply. connected to pin 40 (0.047 ? f bypass) 4 p0.3 individually configured gpio 5 p0.1 individually configured gpio 6v bat1 connect to 1.8 v to 3.6 v power supply, through 47 ohm series/1 ? f shunt c. 8 p2.1 gpio. port 2 bit 1 9v bat2 connected to1.8 v to 3.6 v ma in power supply, through 0.047 ? f bypass c. 10 rf bias rf pin voltage reference 11 rf p differential rf to or from antenna 12 gnd gnd 13 rf n differential rf to or from antenna 14, 17, 18, 20 nc 15 p2.0 gpio 19 resv reserved. must connect to gnd 21 p1.0 gpio port 1 bit 0 / issp-sclk if this pin is used as a general-pur pose output it draws current. it is, therefore, configured as an input to reduce current draw. 22 p1.1 gpio port 1 bit 1 / issp-sdata if this pin is used as a general-pur pose output it draws current. it is, therefore, configured as an input to reduce current draw. 23 v dd_micro mcu supply connected to pin 40, max cpu 12 mhz cyrf69103 document number: 001-07611 rev *i page 7 of 72 functional block overview all the blocks that make up the proc lp are presented in this section. 2.4 ghz radio the radio transceiver is a dual conversion low if architecture optimized for power and range/robustness. the radio employs channel matched filters to achieve high performance in the presence of interference. an integrated power amplifier (pa) provides up to +4 dbm transmit power, with an output power control range of 34 db in eight steps. the supply current of the device is reduced as the rf output power is reduced. frequency synthesizer before transmission or receptio n may commence, it is necessary for the frequency synthesizer to settle. the sett ling time varies depending on channel; 25 fast channels are provided with a maximum settling time of 100 ? s. the ?fast channels? (<100 ? s settling time) are every 3 rd frequency, starting at 2400 mhz up to and including 2472 mhz (that is, 0,3,6,9??.69 and 72). baseband and framer the baseband and framer blo cks provide the dsss encoding and decoding, sop generation and reception and crc16 generation and checking, and eop detection and length field. data transmission modes and data rates the soc supports four different data transmission modes: in gfsk mode, data is transmitted at 1 mbps, without any dsss. in 8dr mode, 8 bits are encoded in each data_code_adr derived code symbol transmitted. in ddr mode, 2 bits are encoded in each data_code_adr derived code symbol transmitted (as in the cywusb6934 ddr mode). in sdr mode, 1 bit is encoded in each data_code_adr derived code symbol transmitted (as in the cywusb6934 standard modes). 24 p1.2 gpio 25 p1.3 / nss slave select 26 p1.4 / sck spi clock 27 irq radio function interrupt output, configure high, low or as radio gpio. 28 p1.5 / mosi mosi pin from microcon troller function to radio function. 29 miso 3-wire spi mode configured as radio gpio. in 4-wire spi mode sends data to mcu function. 30 xout buffered clk, pactl_n or radio gpio. 31 pactl control for external pa or radio gpio. 32 p1.6 gpio 33 v io 1.8 v to 3.6v to main power supply rail for radio i/o. 34 rst radio reset. connected to pin 40 with 0.47 ? f. must have a rst = high event the very first time power is applied to the radio otherwise the stat e of the radio control registers is unknown. 35 p1.7 gpio 36 v dd1.8 regulated logic bypass. connected to 0.47 ? f to gnd. 37 l/d inductor/diode connection for boost. when inte rnal pmu is not being used connect l/d to gnd. 38 p0.7 gpio 39 v bat0 connected to1.8 v to 3.6 v ma in power supply, through 0.047 ? f bypass c. 40 v reg boost regulator output voltage feedback 41 e-pad must be connected to ground. 42 corner tabs do not connect corner tabs. pin definitions (continued) pin name description table 3. internal pa output power step table pa setting typical output power (dbm) 7+4 60 5?5 4?10 3?15 2?20 1?25 0?30 cyrf69103 document number: 001-07611 rev *i page 8 of 72 both 64-chip and 32-chip data_code_adr codes are supported. the four data transmission modes apply to the data after the sop. in particular the length, data, and crc16 are all sent in the same mode. in general, lower data rates reduces packet error rate in any given environment. the cyrf69103 ic supports the following data rates: 1000 kbps (gfsk) 250 kbps (32-chip 8dr) 125 kbps (64-chip 8dr) 62.5 kbps (32-chip ddr) 31.25 kbps (64-chip ddr) 15.625 kbps (64-chip sdr) lower data rates typically provide longer range and/or a more robust link. link layer modes the cyrf69103 ic device supports the following data packet framing features: sop ? packets begin with a 2-symbol start of packet (sop) marker. this is required in gfsk and 8dr modes, but is optional in ddr mode and is not supported in sdr mode. if framing is disabled then an sop event is inferred whenever two successive correlations are detected. the sop_code_adr code used for the sop is different from that used for the ?body? of the packet, and if desired may be a different length. sop must be configured to be the same length on both sides of the link. eop ? there are two options for detecting the end of a packet. if sop is enabled, then a packet length field may be enabled. gfsk and 8dr must enable the length field. this is the first 8 bits after the sop symbol, and is transmitted at the payload data rate. if the length field is enabled, an end of packet (eop) condition is inferred after re ception of the number of bytes defined in the length field, plus two bytes for the crc16 (if enabled). the alternative to using the length field is to infer an eop condition from a configurable number of successive non correlations; this option is not available in gfsk mode and is only recommended when using sdr mode. crc16 ? the device may be configured to append a 16-bit crc16 to each packet. the crc16 uses the usb crc polynomial with the added programmability of the seed. if enabled, the receiver verifies the calculated crc16 for the payload data against the received value in the crc16 field. the starting value for the crc16 calculation is configurable, and the crc16 transmitted may be calcul ated using either the loaded seed value or a zero seed; the received data crc16 is checked against both the configured and zero crc16 seeds. crc16 detects the following errors: any one bit in error any two bits in error (no matter how far apart, which column, and so on) any odd number of bits in error (no matter where they are) an error burst as wide as the checksum itself figure 2 shows an example packet with sop, crc16 and lengths fields enabled. figure 2. example default packet format packet buffers and radio configuration registers packet data and configuration registers are accessed through the spi interface. all confi guration registers are directly addressed through the address field in the spi packet (as in the cywusb6934). configuration registers are provided to allow configuration of dsss pn codes, data rate, operating mode, interrupt masks, interrupt status, and others. packet buffers all data transmission and reception use the 16-byte packet buffers: one for transmission and one for reception. the transmit buffer allows a complete packet of up to 16 bytes of payload data to be loaded in one burst spi transaction, and then transmitted with no further mcu intervention. similarly, the receive buffer allows an entire packet of payload data up to 16 bytes to be received with no firmware intervention required until packet reception is complete. the cyrf69103 ic supports packet length of up to 40 bytes; interrupts are provided to allow an mcu to use the transmit and receive buffers as fifos. when transmitting a packet longer than 16 bytes, the mcu can load 16 bytes initially, and add further bytes to the transmit buffer as transmission of data creates space in the buffer. similarly, when receiving packets longer than 16 bytes, the mcu must fetch received data from the fifo periodically during packet reception to prevent it from overflowing. auto transaction sequencer (ats) the cyrf69103 ic provides automated support for transmission and reception of acknowledged data packets. when transmitting a data packet, the device automatically starts the crystal and synthesizer, enter s transmit mode, transmits the packet in the transmit buffer, and then automatically switches to receive mode and waits for a handshake packet ? and then p sop 1 sop 2 length crc 16 payload data preamble n x 16us 1st fram ing sym bol* 2nd fram ing sym bol* packet length 1 byte period *note:32 or 64us cyrf69103 document number: 001-07611 rev *i page 9 of 72 automatically reverts to sleep mode or idle mode when either an ack packet is received, or a time out period expires. similarly, when receiving in transaction mode, the device waits in receive mode for a valid packet to be received, then automatically transitions to transmit mode, transmits an ack packet, and then switches back to receive mode to await the next packet. the contents of the packet buffers are not affected by the transmission or reception of ack packets. in each case, the entire packet transaction takes place without any need for mcu firmware action; to transmit data the mcu simply needs to load the data packet to be transmitted, set the length, and set the tx go bit. similarly, when receiving packets in transaction mode, firmware simply needs to retrieve the fully received packet in response to an interrupt request indicating reception of a packet. interrupts the radio function provides an in terrupt (irq) output, which is configurable to indicate the occurrence of various different events. the irq pin may be programmed to be either active high or active low, and be either a cmos or open drain output. the radio function features three sets of interrupts: transmit, receive, and system interrupts. these interrupt s all share a single pin (irq), but can be independently enabled/disabled. in transmit mode, all receive interrupts are automatically disabled, and in receive mode all transmit interrupts are automatically disabled. however, the contents of the enable registers are preserved when switching between transmit and receive modes. if more than one radio interrupt is enabled at any time, it is necessary to read the relevant status register to determine which event caused the irq pin to assert. even when a given interrupt source is disabled, the status of the condition that would otherwise cause an interrupt c an be determined by reading the appropriate status register. it is therefore possible to use the devices without making use of the irq pin by polling the status register(s) to wait for an event, rather than using the irq pin. clocks a 12 mhz crystal (30 ppm or better) is directly connected between xtal and gnd without the need for external capacitors. a digital clock out function is provided, with selectable output frequencies of 0. 75, 1.5, 3, 6, or 12 mhz. this output may be used to clock an external microcontroller (mcu) or asic. this output is enabled by default, but may be disabled. the requirements for the crystal to be directly connected to xtal pin and gnd are: nominal frequency: 12 mhz operating mode: fundamental mode resonance mode: parallel resonant frequency initial stability: 30 ppm series resistance: < 60 ohms load capacitance: 10 pf drive level: l00 ? w the mcu function features an internal oscillator. the clock generator provides the 12 mhz and 24 mhz clocks that remain internal to the microcontroller. gpio interface the mcu function features up to 15 general purpose i/o (gpio) pins.the i/o pins are grouped into three ports (port 0 to 2). the pins on port 0 and port 1 may each be configured individually while the pins on port 2 may only be configured as a group. each gpio port supports high-impedance inputs, configurable pull up, open drain output, cmos/ttl inputs, and cmos output with up to two pins that support progr ammable drive strength of up to 50 ma sink current. additionally, each i/o pin can be used to generate a gpio interrupt to the microcontroller. each gpio port has its own gpio interrupt vect or with the exception of gpio port 0. gpio port 0 has th ree dedicated pins that have independent interrupt vect ors (p0.1, p0.3?p0.4). power on reset/low voltage detect the power on reset circuit detects logic when power is applied to the device, resets the logic to a known state, and begins executing instructions at flash address 0x0000. when power falls below a programmable trip voltage, it generates reset or may be configured to generate interrupt. there is a low voltage detect circuit that detects when v cc drops below a programmable trip voltage. it may be configurable to generate an lvd interrupt to inform the processor about the low voltage event. por and lvd share the same interrupt. there is not a separate interrupt for each. the watchdog timer can be used to ensure the firmware never gets stalled in an infinite loop. timers the free running 16-bit timer provides two interrupt sources: the programmable interval timer with 1- ? s resolution and the 1.024 ms outputs. the timer can be used to measure the duration of an event under firmware control by reading the timer at the start and at the end of an event, then calculating the difference between the two values. power management the operating voltage of the device is 1.8v to 3.6v dc, which is applied to the v bat pin. the device can be shut down to a fully static sleep mode by writing to the frc end = 1 and end state = 000 bits in the xa ct_cfg_adr register over the spi interface. the device enters sleep mode within 35 ? s after the last sck positive edge at t he end of this spi transaction. alternatively, the device ma y be configured to automatically enter sleep mode after completing packet transmission or reception. when in sleep mode, t he on-chip oscillator is stopped, but the spi interface remains functional. the device wakes from sleep mode automatically when the device is commanded to enter transmit or receive mode. when resuming from sleep mode, there is a short delay while the oscillator restarts. the device may be configured to assert the irq pin when the oscillator has stabilized. the output voltage (v reg ) of the power management unit (pmu) is configurable to severa l minimum values between 2.4 v and 2.7 v. v reg may be used to provide up to 15 ma (average load) to external devices. it is possible to disable the pmu, and to provide an externally regulated dc supply voltage to the cyrf69103 document number: 001-07611 rev *i page 10 of 72 device in the range 2.4 v to 3.6 v. the pmu also provides a regulated 1.8 v supply to the logic. the pmu has been designed to provide high boost efficiency (74?85% depending on input voltage, output voltage and load) when using a schottky diode and power inductor, eliminating the need for an external boost converter in many systems where other components require a boosted voltage. however, reasonable efficiencies (69?82% depending on input voltage, output voltage and load) may be achieved when using low-cost components such as sot23 diodes and 0805 inductors. the current through the diode must stay within the linear operating range of the diode. for some loads the sot23 diode is sufficient, but with higher loads it is not and a ss12 diode must be used to stay within this linear range of operation. along with the diode, the inductor used must not saturate its core. in higher loads, a lower resistance/higher saturation coil like the inductor from sumida must be used. the pmu also provides a conf igurable low battery detection function which may be read over the spi interface. one of seven thresholds between 1.8 v and 2.7 v may be selected. the interrupt pin may be configured to assert when the voltage on the v bat pin falls below the configured threshold. lv irq is not a latched event. battery monitoring is disabled when the device is in sleep mode. the following three figures show different examples of how to use proc lp with and without the pmu. figure 3 shows the most common circuit making use of the pmu to boost battery voltage up to 2.7 v. figure 4 is an example of the circuit used when the supply voltage is always above 2.7 v. this could be three 1.5 v battery cells in series along with a linear regulator, or some similar power source. figure 5 shows an example of using the proc lp with its pmu disabled and an external boost to supply power to the device. this might be required when the load is much greater than the 15 ma average load that proc can support. figure 3. pmu enabled figure 4. pmu disabled - linear regulator proc lp l/d 10 f 6.3v v cc 100 f 10v v bat bat400d 10 h v reg v bat0 v bat1 v bat2 v cc1 v cc2 v cc3 v io v cc v bat 0.047 f 0.047 f 0.047 f 0.047 f 0.047 f 10 f 6.3v 1 f 6.3v 0.047f 1 ohm 1% 47 ohm v dd_micro v dd 0.1f proc lp v reg v bat0 v bat1 v bat2 v cc1 v cc2 v cc3 l/d v io v cc 0.047f 0.047f 0.047f 0.047f 0.047f 0.047f 0.047f 0.047f v dd_micro v dd 0.1f cyrf69103 document number: 001-07611 rev *i page 11 of 72 figure 5. pmu disabled - external bo ost converter low noise amplifier (lna) and received signal strength indication (rssi) the gain of the receiver may be controlled directly by clearing the agc en bit and writing to t he low noise amplifier (lna) bit of the rx_cfg_adr register. when the lna bit is cleared, the receiver gain is reduced by approximately 20 db, allowing accurate reception of very strong received signals (for example when operating a receiver very close to the transmitter). an additional 20 db of receiver attenuation can be added by setting the attenuation (att) bit; this a llows data reception to be limited to devices at very short ranges. disabling agc and enabling lna is recommended unless receiving from a device using external pa. the rssi register returns the relative signal strength of the on-channel signal power. when receiving, the device may be configured to automatically measure and store the relative strength of the signal being received as a 5-bit value. when enabled, an rssi reading is taken and may be read through the spi interface. an rssi reading is taken automatically when the start of a packet is detected. in addition, a new rssi reading is taken every time the previous reading is read from the rssi register, allowing the background rf energy level on any given channel to be easily measured when rssi is read when no signal is being received. a new reading can occur as fast as once every 12 ? s. receive spurious response the transmitter may exhibit spurs around 50mhz offset at levels approximately 50db to 60db below the carrier power. receivers operating at the transmit spur frequency may receive the spur if the spur level power is greater than the receive sensitivity level. the workaround for this is to program an additional byte in the packet header which contains the transmitter channel number. after the packet is received, the channel number can be checked. if the channel number does not match the receive channel then the packet is rejected. spi interface the spi interface between the mcu function and the radio function is a 3-wire spi interface. the three pins are mosi (master out slave in), sck (s erial clock), ss (slave select). there is an alternate 4-wire miso interface that requires the connection of two external pins. the spi interface is controlled by configuring the spi configur e register. (spicr addr: 0x3d). 3-wire spi interface the radio function receives a cl ock from the mcu function on the sck pin. the mosi pin is multiplexed with the miso pin. bidirectional data transfer takes place between the mcu function and the radio function through th is multiplexed mosi pin. when using this mode the user firmware must ensure that the mosi pin on the mcu function is in a hi gh impedance state, except when the mcu is actively transmitting data. firmware must also control the direction of data flow and switch directions between mcu function and radio function by setting the swap bit [bit 7] of the spi configure register. the ss pi n is asserted before initiating a data transfer between the mcu function and the radio function. the irq function may be optionally multiplexed with the mosi pin; when this option is enabled the irq function is not available while the ss pin is low. when us ing this configuration, user firmware must ensure that the mosi function on mcu function is in a high-impedance state whenever ss is high. figure 6. 3-wire spi mode 4-wire spi interface the 4-wire spi communications interface consists of mosi, miso, sck, and ss. proc lp l/d v reg v bat0 v bat1 v bat2 v cc1 v cc2 v cc3 v io v cc v bat 0.047f 0.047f 0.047f 0.047f 0.047f 10f 6.3v 1f 6.3v 0.047f 1 ohm 1% 47 ohm external dc-dc boost converter v dd_micro v dd 0.1f mcu function p1.5/mosi p1.4/sck p1.3/nss mosi sck nss radio function mosi sck nss mosi/miso multiplexed on one mosi pin cyrf69103 document number: 001-07611 rev *i page 12 of 72 the device receives sck from the mcu function on the sck pin. data from the mcu function is sh ifted in on the mosi pin. data to the mcu function is shifted ou t on the miso pin. the active low ss pin must be asserted for the two functions to communicate. the irq function may be optionally multiplexed with the mosi pin; when this option is enabled the irq function is not available while the ss pin is low. when using this configuration, user firmware must ensure that the mosi function on mcu function is in a high-impedance state whenever ss is high. figure 7. 4-wire spi mode spi communication and transactions the spi transactions can be single byte or multi-byte. the mcu function initiates a data transfer through a command/address byte. the following bytes are data bytes. the spi transaction format is shown in figure 4 . the dir bit specifies the direction of data transfer. 0 = master reads from slave. 1 = master writes to slave. the inc bit helps to read or write consecutive bytes from contiguous memory locations in a single burst mode operation. if slave select is asserted and inc = 1, then the master mcu function reads a byte from the radio, the address is incremented by a byte location, and then the byte at that location is read, and so on. if slave select is asserted and inc = 0, then the mcu function reads/writes the bytes in the same register in burst mode, but if it is a register file then it reads/w rites the bytes in that register file. the spi interface between the radio function and the mcu is not dependent on the internal 12 mhz oscillator of the radio. therefore, radio function registers can be read from or written into while the radio is in sleep mode. spi i/o voltage references the spi interfaces between mcu function and the radio and the irq and rst have a separate voltage reference v io . for cyrf69103 v io is normally set to v cc . spi connects to external devices the three spi wires, mosi, sck, and ss are also drawn out of the package as external pins to allow the user to interface their own external devices (such as optical sensors and others) through spi. the radio function also has its own spi wires miso and irq, which can be used to send data back to the mcu function or send an interrupt request to the mcu function. they can also be configured as gpio pins. mcu function p1.5/mosi p1.4/sck p1.3/nss p1.6/miso mosi sck nss radio function miso mosi sck nss this connection is external to the proc lp chip table 4. spi transaction format byte 1 byte 1+n bit # 7 6 [5:0] [7:0] bit name dir inc address data cyrf69103 document number: 001-07611 rev *i page 13 of 72 cpu architecture this family of microcontrollers is based on a high-performance, 8-bit, harvard architecture microp rocessor. five registers control the primary operation of the cp u core. these registers are affected by various instructions, but are not directly accessible through the register space by the user. the 16-bit program counter register (cpu_pc) allows for direct addressing of the full eight kb ytes of program memory space. the accumulator register (cpu_a) is the general-purpose register that holds the results of instructions that specify any of the source addressing modes. the index register (cpu_x) holds an offset value that is used in the indexed addressing modes. typically, this is used to address a block of data within the data memory space. the stack pointer register (cpu_sp) holds the address of the current top-of-stack in the data memory space. it is affected by the push, pop, lcall, call, reti, and ret instructions, which manage the software stack. it can also be affected by the swap and add instructions. the flag register (cpu_f) has three status bits: zero flag bit [1]; carry flag bit [2]; supervisory state bit [3]. the global interrupt enable bit [0] is used to globally enable or disable interrupts. the user cannot manipulate the supervisory state status bit [3]. the flags are affect ed by arithmetic, logic, and shift operations. the manner in which each flag is changed is dependent upon the instruction being executed (for example, and, or, xor). see table 22 on page 19. table 5. cpu registers and register name register register name flags cpu_f program counter cpu_pc accumulator cpu_a stack pointer cpu_sp index cpu_x cyrf69103 document number: 001-07611 rev *i page 14 of 72 cpu registers flags register the flags register can only be set or reset with logical instruction. accumulator register table 6. cpu flags register (cpu_f) [r/w] bit # 7 6 5 4 3 2 1 0 field reserved xio super carry zero global ie read/write ? ? ? r/w r rwrwrw default 00000010 bits 7:5 reserved bit 4 xio set by the user to select between the register banks. 0 = bank 0 1 = bank 1 bit 3 super indicates whether the cpu is executing user code or supervisor code (this code cannot be accessed directly by the user). 0 = user code 1 = supervisor code bit 2 carry set by cpu to indicate whether there has been a ca rry in the previous logi cal/arithmetic operation. 0 = no carry 1 = carry bit 1 zero set by cpu to indicate whether there has been a zero result in the previous logical/arithmetic operation. 0 = not equal to zero 1 = equal to zero bit 0 global ie determines whether all interrupts are enabled or disabled. 0 = disabled 1 = enabled note this register is readable with explicit address 0xf7. the or f, expr and and f, expr must be used to set and clear the cpu_f bits. table 7. cpu accumulator register (cpu_a) bit # 7 6 5 4 3 2 1 0 field cpu accumulator [7:0] read/write ???????? default 00000000 bits 7:0 cpu accumulator [7:0] 8-bit data value holds the result of any logical/arithmetic in struction that uses a source addressing mode. cyrf69103 document number: 001-07611 rev *i page 15 of 72 index register stack pointer register cpu program counter high register cpu program counter low register table 8. cpu x register (cpu_x) bit # 7 6 5 4 3 2 1 0 field x [7:0] read/write ???????? default 00000000 bits 7:0 x [7:0] 8-bit data value holds an index for any instruction that uses an indexed addressing mode. table 9. cpu stack pointer register (cpu_sp) bit # 7 6 5 4 3 2 1 0 field stack pointer [7:0] read/write ???????? default 00000000 bits 7:0 stack pointer [7:0] 8-bit data value holds a pointer to the current top-of-stack. table 10. cpu program coun ter high register (cpu_pch) bit # 7 6 5 4 3 2 1 0 field program counter [15:8] read/write ???????? default 00000000 bits 7:0 program counter [15:8] 8-bit data value holds the higher byte of the program counter. table 11. cpu program counter low register (cpu_pcl) bit # 7 6 5 4 3 2 1 0 field program counter [7:0] read/write ???????? default 00000000 bit 7:0 program counter [7:0] 8-bit data value holds the lower byte of the program counter. cyrf69103 document number: 001-07611 rev *i page 16 of 72 addressing modes examples of the different addressing modes are discussed in this section and example code is given. source immediate the result of an instruction using this addressing mode is placed in the a register, the f register, the sp register, or the x register, which is specified as part of the instruction opcode. operand 1 is an immediate value that serves as a source for the instruction. arithmetic instructions require two sources. instructions using this addressing mode are two bytes in length. examples source direct the result of an instruction using this addressing mode is placed in either the a register or the x register, which is specified as part of the instruction opcode. operand 1 is an address that points to a location in either the ram memo ry space or the register space that is the source for the inst ruction. arithmetic instructions require two sources; the second so urce is the a register or x register specified in the op code. instructions using this addressing mode are two bytes in length. examples source indexed the result of an instruction us ing this addressing mode is placed in either the a register or the x register, which is specified as part of the instruction opcode. operand 1 is added to the x register forming an address that points to a location in either the ram memory space or the register space that is the source for the instruction. arithmetic instruct ions require two sources; the second source is the a register or x register specified in the opcode. instructions using this addressing mode are two bytes in length. examples destination direct the result of an instruction us ing this addressing mode is placed within either the ram memory space or the register space. operand 1 is an address that points to the location of the result. the source for the instruction is either the a register or the x register, which is specified as part of the instruction opcode. arithmetic instructions require two sources; the second source is the location specified by operand 1. instructions using this addressing mode are two bytes in length. examples table 12. source immediate opcode operand 1 instruction immediate value add a, 7 in this case, the immediate value of 7 is added with the accumulator, and the result is placed in the accumulator. mov x, 8 in this case, the immediate value of 8 is moved to the x register. and f, 9 in this case, the immediate value of 9 is logically anded with the f register and the result is placed in the f register. table 13. source direct opcode operand 1 instruction source address add a, [7] in this case, the value in the ram memory location at address 7 is added with the accumulator, and the result is placed in the accumulator. mov x, reg[8] in this case, the value in the register space at address 8 is moved to the x register. table 14. source indexed opcode operand 1 instruction source index add a, [x+7] in this case, the value in the memory location at address x + 7 is added with the accumulator, and the result is placed in the accumulator. mov x, reg[x+8] in this case, the value in the register space at address x + 8 is moved to the x register. table 15. destination direct opcode operand 1 instruction destination address add [7], a in this case, the value in the memory location at address 7 is added with the accumulator, and the result is placed in the memory location at address 7. the accumulator is unchanged. mov reg[8], a in this case, the accumulator is moved to the register space location at address 8. the accumulator is unchanged. cyrf69103 document number: 001-07611 rev *i page 17 of 72 destination indexed the result of an instruction using this addressing mode is placed within either the ram memory space or the register space. operand 1 is added to the x register forming the address that points to the location of the resu lt. the source for the instruction is the a register. arithmetic inst ructions require two sources; the second source is the location s pecified by operand 1 added with the x register. instructions using this addressing mode are two bytes in length. example destination direct source immediate the result of an instruction using this addressing mode is placed within either the ram memory space or the register space. operand 1 is the address of the result. the source for the instruction is operand 2, which is an immediate value. arithmetic instructions require two sources; the second source is the location specified by operand 1. instructions using this addressing mode are three bytes in length. examples destination indexed source immediate the result of an instruction us ing this addressing mode is placed within either the ram memory space or the register space. operand 1 is added to the x register to form the address of the result. the source for the instru ction is operand 2, which is an immediate value. arithmetic instru ctions require two sources; the second source is the location specified by operand 1 added with the x register. instructions using this addressing mode are three bytes in length. examples destination direct source direct the result of an instruction us ing this addressing mode is placed within the ram memory. operand 1 is the address of the result. operand 2 is an address that points to a location in the ram memory that is the source for the instruction. this addressing mode is only valid on the mov instruction. the instruction using this addressing mode is three bytes in length. example table 16. destination indexed opcode operand 1 instruction destination index add [x+7], a in this case, the value in the memory location at address x+7 is added with the accumulator, and the result is placed in the memory location at address x+7. the accumulator is unchanged. table 17. destination direct source immediate opcode operand 1 operand 2 instruction destination address immediate value add [7], 5 in this case, value in the memory location at address 7 is added to the immediate value of 5, and the result is placed in the memory location at address 7. mov reg[8], 6 in this case, the immediate value of 6 is moved into th e register space location at address 8. table 18. destination indexed source immediate opcode operand 1 operand 2 instruction destination index immediate value add [x+7], 5 in this case, the value in the memory location at address x+7 is added with the immediate value of 5 and the result is placed in the memory location at address x+7. mov reg[x+8], 6 in this case, the immediate value of 6 is moved into the location in the register space at address x+8. table 19. destination direct source direct opcode operand 1 operand 2 instruction destination address source address mov [7], [8] in this case, the value in the memory location at address 8 is moved to the memory location at address 7. cyrf69103 document number: 001-07611 rev *i page 18 of 72 source indirect post increment the result of an instruction using this addressing mode is placed in the accumulator. operand 1 is an address pointing to a location within the memory spac e, which contains an address (the indirect address) for the s ource of the instruction. the indirect address is incremented as part of the instruction execution. this addressing mode is only valid on the mvi instruction. the instruction using this addressing mode is two bytes in length. refer to the psoc designer: assembly language user guide for further details on mvi instruction. example destination indirect post increment the result of an instruction us ing this addressing mode is placed within the memory space. operand 1 is an address pointing to a location within the memory space, which contains an address (the indirect address) for the de stination of the instruction. the indirect address is incremente d as part of the instruction execution. the source for the instruction is the accumulator. this addressing mode is only valid on the mvi instruction. the instruction using this addressing mode is two bytes in length. example table 20. source indirect post increment opcode operand 1 instruction source address address mvi a, [8] in this case, the value in the memory location at address 8 is an indirect address. the memory location pointed to by the indirect address is moved into the accumulator. the indirect address is then incremented. table 21. destination indirect post increment opcode operand 1 instruction destination address address mvi [8], a in this case, the value in the memory location at address 8 is an indirect address. the accu mulator is moved into the memory location pointed to by the indirect address. the indirect address is then incremented. cyrf69103 document number: 001-07611 rev *i page 19 of 72 instruction set summary the instruction set is summarized in ta b l e 2 2 numerically and serves as a quick reference. if more information is needed, the instruction set summary tables are described in detail in the psoc designer assembly language user guide (available on www.cypress.com ). table 22. instruction set summary sorted numerically by opcode order [1, 2] opcode hex cycles bytes instruction format flags opcode hex cycles bytes instruction format flags opcode hex cycles bytes instruction format flags 00 15 1 ssc 2d 8 2 or [x+expr], a z 5a 5 2 mov [expr], x 01 4 2 add a, expr c, z 2e 9 3 or [expr], expr z 5b 4 1 mov a, x z 02 6 2 add a, [expr] c, z 2f 10 3 or [x+expr], expr z 5c 4 1 mov x, a 03 7 2 add a, [x+expr] c, z 30 9 1 halt 5d 6 2 mov a, reg[expr] z 04 7 2 add [expr], a c, z 31 4 2 xor a, expr z 5e 7 2 mov a, reg[x+expr] z 05 8 2 add [x+expr], a c, z 32 6 2 xor a, [expr] z 5f 10 3 mov [expr], [expr] 06 9 3 add [expr], expr c, z 33 7 2 xor a, [x+expr] z 60 5 2 mov reg[expr], a 07 10 3 add [x+expr], expr c, z 34 7 2 xor [expr], a z 61 6 2 mov reg[x+expr], a 08 4 1 push a 35 8 2 xor [x+expr], a z 62 8 3 mov reg[expr], expr 09 4 2 adc a, expr c, z 36 9 3 xor [expr], expr z 63 9 3 mov reg[x+expr], expr 0a 6 2 adc a, [expr] c, z 37 10 3 xor [x+expr], expr z 64 4 1 asl a c, z 0b 7 2 adc a, [x+expr] c, z 38 5 2 add sp, expr 65 7 2 asl [expr] c, z 0c 7 2 adc [expr], a c, z 39 5 2 cmp a, expr if (a=b) z=1 if (a cyrf69103 document number: 001-07611 rev *i page 21 of 72 data memory organization the mcu function provides up to 256 bytes of data ram. figure 9. data memory organization flash this section describes the flas h block of the cyrf69103. much of the user visible flash functionality, including programming and security, are implemented in the m8c supervisory read only memory (srom). cyrf69103 flash has an endurance of 1000 cycles and 10-year data retention. flash programming and security all flash programming is performed by code in the srom. the registers that control the flash programming are only visible to the m8c cpu when it is executing out of srom. this makes it impossible to read, write, or erase the flash by bypassing the security mechanisms implemented in the srom. customer firmware can only program the flash through srom calls. the data or code images can be sourced by way of any interface with the appropriate support firmware. this type of programming requires a ?bootloader? ? a piece of firmware resident on the flash. for safety reasons, this bootloader must not be over written during firmware rewrites. the flash provides four auxiliary rows that are used to hold flash block protection flags, boot time calibration values, configuration tables, and any device values. the routines for accessing these auxiliary rows are documented in the srom section. the auxiliary rows are not affected by the device erase function. in-system programming cyrf69103 enables this type of in-system programming by using the p1.0 and p1.1 pins as the serial programming mode interface. this allows an external controller to cause the cyrf69103 to enter serial programming mode and then to use the test queue to issue flash access functions in the srom. srom the srom holds code that is us ed to boot the part, calibrate circuitry, and perform flash operations ( ta b l e 2 3 lists the srom functions). the functions of the srom may be accessed in normal user code or operating fr om flash. the srom exists in a separate memory space from user code. the srom functions are accessed by executing the supervisory system call instruction (ssc), which has an opcode of 00h. before executing the ssc, the m8c?s accumulator needs to be loaded with the desired srom function code from ta b l e 2 3 . undefined functions causes a halt if called from user code. the srom functions are executing code with calls; t herefore, the functions require stack space. with the exception of reset, all of the srom functions have a parameter block in sram that must be configured before executing the ssc. table 24 on page 22 lists all possible parameter block variables. the meaning of each parameter, with regards to a specific srom function, is described later in this section. after reset address 8-bit psp 0x00 stack begins here and grows upward top of ram memory 0xff table 23. srom function codes function code function name stack space 00h swbootreset 0 01h readblock 7 02h writeblock 10 03h eraseblock 9 05h eraseall 11 06h tableread 3 07h checksum 3 cyrf69103 document number: 001-07611 rev *i page 22 of 72 two important variables that ar e used for all functions are key1 and key2. these variables are used to help discriminate between valid sscs and inadvertent sscs. key1 must always have a value of 3ah, while key2 must have the same value as the stack pointer when the srom function begins execution. this is the stack pointer value when the ssc opcode is executed, plus three. if either of the keys do not match the expected values, the m8c halts (with the exception of the swbootreset function). the following code puts the correct value in key1 and key2. the code st arts with a halt, to force the program to jump directly into the setup code and not run into it. halt sscop: mov [key1], 3ah mov x, sp mov a, x add a, 3 mov [key2], a the srom also features return codes and lockouts. return codes return codes aid in the determination of success or failure of a particular function. the return code is stored in key1?s position in the parameter block. the checksum and tableread functions do not have return codes because key1?s position in the parameter block is used to return other data. read, write, and erase operations may fail if the target block is read or write protected. block protection levels are set during device programming. the eraseall function overwrites data in addition to leaving the entire user flash in the erase st ate. the eraseall function loops through the number of flash macros in the product, executing the following sequence: erase, bulk program all zeros, erase. after all the user space in all the flash macros are erased, a second loop erases and then programs each protection block with zeros. srom function descriptions all srom functions are described in the following sections. swbootreset function the srom function, swbootreset, is the function that is responsible for transitioning the device from a reset state to running user code. the swbootreset function is executed whenever the srom is entered with an m8c accumulator value of 00h; the sram parameter block is not used as an input to the function. this happens, by design, after a hardware reset, because the m8c's accumulator is reset to 00h or when user code executes the ssc instruction with an accumulator value of 00h. the swbootreset function does not execute when the ssc instruction is executed with a bad key value and a nonzero function code. a cyrf69103 device executes the halt instruction if a bad value is given for either key1 or key2. the swbootreset function verifies the integrity of the calibration data by way of a 16-bit checksum, before releasing the m8c to run user code. readblock function the readblock function is used to read 64 contiguous bytes from flash ? a block. the first thing this function does is to check the protection bits and determine if the desired blockid is readable. if read protection is turned on, the readblock function exits setting the accumulator and key2 back to 00h. key1 has a value of 01h, indicating a read failure. if read protection is not enabled, the function reads 64 bytes from the flash using a romx instruction and store the results in sram using an mvi instruction. the first of the 64 bytes are stored in sram at the address indicated by the value of the pointer parameter. when the readblock completes successfully, the a ccumulator, key1 and key2, all have a value of 00h. writeblock function the writeblock function is used to store data in the flash. data is moved 64 bytes at a time from sram to flash using this function. the first thing the writeblock function does is to check the protection bits and determine if the desired blockid is writable. if write protection is turned on, the writeblock function exits, setting the a ccumulator and key2 ba ck to 00h. key1 has a value of 01h, indicating a write failure. the configuration of the writeblock function is straightforward. the blockid of the flash block, where the data is stored, must be determined and stored at sram address fah. the sram address of the first of the 64 bytes to be stored in flash must be indicated using the pointer variable in the table 24. srom function parameters variable name sram address key1/counter/return code 0,f8h key2/tmp 0,f9h blockid 0,fah pointer 0,fbh clock 0,fch mode 0,fdh delay 0,feh pcl 0,ffh table 25. srom return codes return code description 00h success 01h function not allowed due to level of protection on block 02h software reset without hardware reset 03h fatal error, srom halted table 26. readblock parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value, when ssc is executed blockid 0,fah flash block number pointer 0,fbh first of 64 addresses in sram where returned data must be stored cyrf69103 document number: 001-07611 rev *i page 23 of 72 parameter block (sram address fbh). finally, the clock and delay values must be set correctly. the clock value determines the length of the write pulse that is used to store the data in the flash. the clock and delay values are dependent on the cpu. refer to ?clocking? section for additional information. eraseblock function the eraseblock function is used to erase a block of 64 contiguous bytes in flash. the first thing the eraseblock function does is to check the protection bits and determine if the desired blockid is writable. if write protection is turned on, the eraseblock function exits, se tting the accumulator and key2 back to 00h. key1 has a value of 01h, indicating a write failure. the eraseblock function is only useful as the first step in programming. erasing a block does not cause data in a block to be one hundred percent unreadab le. if the objective is to obliterate data in a block, the best method is to perform an eraseblock followed by a writeblock of all zeros. to set up the parameter block for the eraseblock function, correct key values must be stored in key1 and key2. the block number to be erased must be stored in the blockid variable and the clock and delay values must be set based on the current cpu speed. protectblock function the cyrf69103 device offers flash protection on a block-by-block basis. table 29 lists the protection modes available. in the table, er and ew are used to indicate the ability to perform external reads and writes. for internal writes, iw is used. internal reading is always permitted by way of the romx instruction. the ability to read by way of the srom readblock function is indicated by sr. the pr otection level is stored in two bits, according to table 29 . these bits are bit packed into the 64 bytes of the protection block. th erefore, each protection block byte stores the protection level fo r four flash blocks. the bits are packed into a byte, with the lowest numbered block?s protection level stored in the lowest numbered bits. the first address of the protecti on block contains the protection level for blocks 0 through 3; t he second address is for blocks 4 through 7. the 64th byte stores the protection level for blocks 252 through 255. the level of protection is only decreased by an eraseall, which places zeros in all locations of the protection block. to set the level of protection, the protectblock function is used. this function takes data from sram, starting at address 80h, and ors it with the current values in the protection block. the result of the or operation is then stored in the protection block. the eraseblock function does not change the protection level for a block. because the sram location for the protection data is fixed and there is only one protection block per flash macro, the protectblock function expects very few variables in the parameter block to be set before calling the function. the parameter block values that must be set, besides the keys, are the clock and delay values. eraseall function the eraseall function performs a series of steps that destroy the user data in the flash macros and resets the protection block in each flash macro to all zeros (the unprotected state). the eraseall function does not affect the three hidden blocks above table 27. writeblock parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value, when ssc is executing block id 0,fah 8 kb flash block number (00h?7fh) 4 kb flash block number (00h?3fh) 3 kb flash block number (00h?2fh) pointer 0,fbh first 64 addresses in sram where the data to be stored in flash is located before calling writeblock clock 0,fch clock divider used to set the write pulse width delay 0,feh for a cpu speed of 12 mhz set to 56h table 28. eraseblock parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointe r value when ssc is executed blockid 0,fah flash block number (00h?7fh) clock 0,fch clock divider used to set the erase pulse width delay 0,feh for a cpu speed of 12 mhz set to 56h table 29. protection modes mode settings description marketing 00b sr er ew iw unprotected unprotected 01b sr er ew iw read protect factory upgrade 10b sr er ew iw disable external write field upgrade 11b sr er ew iw disable internal write full protection 76543210 block n+3 block n+2 block n+1 block n table 30. protectblock parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value when ssc is executed clock 0,fch clock divider used to set the write pulse width delay 0,feh for a cpu speed of 12 mhz set to 56h cyrf69103 document number: 001-07611 rev *i page 24 of 72 the protection block in each flas h macro. the first of these four hidden blocks is used to store the protection table for its eight kbytes of user data. the eraseall function begins by erasing the user space of the flash macro with the highest address range. a bulk program of all zeros is then performed on the same flash macro, to destroy all traces of the previo us contents. the bulk program is followed by a second erase that leaves the flash macro in a state ready for writing. the erase, program, erase sequence is then performed on the next lowest flash macro in the address space if it exists. following the erase of the user space, the protection block for the flash macro with the highest address range is erased. following the erase of the protection block, zeros are written into every bit of the protection table. the next lowest flash macro in the address space then has its protection block erased and filled with zeros. the end result of the eraseall function is that all user data in the flash is destroyed and t he flash is left in an unpro- grammed state, ready to accept one of the various write commands. the protection bits for all user data are also reset to the zero state. the parameter block values that must be set, besides the keys, are the clock and delay values. tableread function the tableread function gives the user access to part specific data stored in the flash during manufacturing. it also returns a revision id for the die (not to be confused with the silicon id). the table space for the cyrf69103 is simply a 64 byte row broken up into eight tables of eight bytes. the tables are numbered zero through seven. all user and hi dden blocks in the cyrf69103 consist of 64 bytes. an internal table holds the silicon id and returns the revision id. the silicon id is returned in sram, while the revision id is returned in the cpu_a and cpu_x registers. the silicon id is a value placed in the table by programming the flash and is controlled by cypress semiconductor product engineering. the revision id is hard coded into the srom. the revision id is discussed in more detail later in this section. an internal table holds alternate trim values for the device and returns a one-byte internal revision counter. the internal revision counter starts out with a value of zero and is incre- mented each time one of the other revision numbers is not incremented. it is reset to zero each time one of the other revision numbers is incremented. the internal revision count is returned in the cpu_a register. the cpu_x register is always set to ffh when trim values are read. the blockid value, in the parameter block, is used to indicate which table must be returned to the user. only the three least significant bits of the blockid parameter are used by the tableread function for the cyrf69103. the upper five bits are ignored. when the function is called, it transfers bytes from the table to sram addresses f8h?ffh. the m8c?s a and x registers are used by the tableread function to return the die?s revi sion id. the revision id is a 16-bit value hard coded into the srom that uniquely identifies the die?s design. checksum function the checksum function calculates a 16-bit checksum over a user specifiable number of blo cks, within a single flash macro (bank) starting from block zero. the blocki d parameter is used to pass in the number of blocks to calculate the checksum over. a blockid value of 1 calculates the checksum of only blo ck 0, while a blockid value of 0 calcu- lates the checksum of all 256 user blocks. the 16-bit checksum is returned in key1 and key2. the parameter key1 holds the lower eight bi ts of the checksum and the parameter key2 holds the upper eight bits of the checksum. the checksum algorithm executes the following sequence of three instructions over the number of blocks times 64 to be checksummed. romx add [key1], a adc [key2], 0 table 31. eraseall parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value when ssc is executed clock 0,fch clock divider used to set the write pulse width delay 0,feh for a cpu speed of 12 mhz set to 56h table 32. table read parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value when ssc is executed blockid 0,fah table number to read table 33. checksum parameters name address description key1 0,f8h 3ah key2 0,f9h stack pointer value when ssc is executed blockid 0,fah number of flash blocks to calculate checksum on cyrf69103 document number: 001-07611 rev *i page 25 of 72 clocking the cyrf69103 internal oscillator outputs two frequencies, the internal 24 mhz oscillator and the 32 khz low power oscillator. the internal 24 mhz oscillator is designed such that it may be trimmed to an output frequency of 24 mhz over temperature and voltage variation. the internal 24 mhz oscillator accuracy is 24 mhz ?22% to +10% (between 0 c?70 c). no external compo- nents are required to achieve this level of accuracy. firmware is responsible for selecting the correct trim values from the user row to match the power supply voltage in the end appli- cation and writing the values to the trim registers iosctr and lposctr. the internal low speed oscillator of nominally 32 khz provides a slow clock source for the cyrf69103 in suspend mode. this is used to generate a periodic wake up interrupt and provide a clock to sequential logic during power up and power down events when the main clock is stopped. in addition, this oscillator can also be used as a clocking source for the interval timer clock (itmrclk) and capture timer clock (tcapclk). the 32 khz low power oscillator can operate in low power mode or can provide a more accurate clock in normal mode. the internal 32 khz low power oscillator accuracy ranges from ?53.12% to +56.25%. the 32 khz low power oscillator can be calibrated against the internal 24 mhz oscill ator or another timing source if desired. cyrf69103 provides the ability to load new trim values for the 24 mhz oscillator based on voltage. this allows vdd to be monitored and have firmware trim the oscillator based on voltage present. the iosctr register is us ed to set trim values for the 24 mhz oscillator. cyrf69103 is initialized with 3.30v trim values at power on, then firmware is responsible for transferring the correct set of trim values to the trim registers to match the application?s actual vdd. the 32 khz oscillator generally does not require trim adjustments versus voltage but trim values for the 32 khz are also stored in supervisory rom. figure 10. srom table to improve the accuracy of the imo, new trim values are loaded based on supply voltage to the part. for this, firmware needs to make modifications to two registers: 1. the internal oscillator trim register at location 0x34. 2. the gain register at location 0x38. val id o p er a t i n g reg i o n f8h f9h fah fbh fch fdh feh ffh table 0 table 1 table 2 table 3 table 4 table 5 table 6 table 7 silicon id [15-8] silicon id [7-0] 24 mhz iosctr at 3.30v 24 mhz iosctr at 3.00v 24 mhz iosctr at 2.85v 24 mhz iosctr at 2.70v 32 khz lposctr at 3.30v 32 khz lposctr at 3.00v 32 khz lposctr at 2.85v 32 khz lposctr at 2.70v cyrf69103 document number: 001-07611 rev *i page 26 of 72 trim values for the iosctr register: the trim values are stored in srom tables in the part as shown in figure 10 on page 25. the trim values are read out from the part based on voltage settings and written to the iosctr register at location 0x34. the f ollowing pseudo code shows how this is done. _main: mov a, 2 mov [ssc_blockid], a call srom operation to read the srom table (refer to section srom table read description ) //after this command is executed, the trim values for 3.3, 3.0, 2.85 and 2.7 are stored at locations fc through ff in the ram. srom calls are explained in the previous section of this datasheet ; mov a, [fch] // trim values for 3.3v mov a, [fdh] // trim values for 3.0v ; mov a, [feh] // trim values for 2.85v ; mov a, [ffh] // trim values for 2.70v mov reg[iosctr],a // loading iosctr with trim values for 3.0v .terminate: jmp .terminate srom table read description the silicon ids for cyrf69103 devices are stored in srom tables in the part, as shown in figure 10 on page 25. the silicon id can be read out from the part using srom table reads. this is demonstrated in the following pseudo code. as mentioned in the section srom on page 21, the srom variables occupy address f8h through ffh in the sram. each of the variables and their definition in given in the section srom on page 21. area sscparmblka(ram,abs) org f8h // variables are defined starting at address f8h ssc_key1: ; f8h supervisory key ssc_returncode: blk 1 ; f8h result code ssc_key2 : blk 1 ;f9h supervisory stack ptr key ssc_blockid: blk 1 ; fah block id ssc_pointer: blk 1 ; fbh pointer to data buffer ssc_clock: blk 1 ; fch clock ssc_mode: blk 1 ; fdh clockw clocke multiplier ssc_delay: blk 1 ; feh flash macro sequence delay count ssc_write_resultcode: blk 1 ; ffh temporary result code _main: mov a, 0 mov [ssc_blockid], a// to read from table 0 - silicon id is stored in table 0 //call srom operation to read the srom table mov x, sp ; copy sp into x mov a, x ; a temp stored in x add a, 3 ; create 3 byte stack frame (2 + pushed a) mov [ssc_key2], a ; save stack frame for supervisory code ; load the supervisory code for flash operations mov [ssc_key1], 3ah ;flash_oper_key - 3ah mov a,6 ; load a with specific operation. 06h is the code for table read table 23 on page 21 ssc ; ssc call the supervisory rom // at the end of the ssc command the silicon id is stored in f8 (msb) and f9(lsb) of the sram .terminate: jmp .terminate cyrf69103 document number: 001-07611 rev *i page 27 of 72 gain value for the register at location [0x38]: 3.3 v = 0x40 3.0 v = 0x40 2.85 v = 0xff 2.70 v = 0xff load register [0x38] with the gain values corresponding to the appropriate voltage. when using the 32 khz oscillator the pitmrl/h must be read until two consecutive readings match before sending/receiving data. the following firmware example assumes the developer is interested in the lower byte of the pit. read_pit_counter: mov a, reg[pitmrl] mov [57h], a mov a, reg[pitmrl] mov [58h],a mov [59h], a mov a, reg[pitmrl] mov [60h], a ;;;start comparison mov a,[60h] mov x, [59h] sub a, [59h] jz done mov a, [59h] mov x, [58h] sub a, [58h] jz done mov x, [57h] ;;;correct data is in memory location 57h done: mov [57h], x ret clock architecture description the cyrf69103 clock selection ci rcuitry allows the selection of independent clocks for the cpu, interval timers, and capture timers. cpu clock the cpu clock, cpuclk, can be sourced from the internal 24 mhz oscillator. the selected clock source can optionally be divided by 2 n-1 where n is 0?7 (see table 36 on page 28). table 34. oscillator trim values vs. voltage settings supervisory rom table function table2 fch 24 mhz iosctr at 3.30 v table2 fdh 24 mhz iosctr at 3.00 v table2 feh 24 mhz iosctr at 2.85 v table2 ffh 24 mhz iosctr at 2.70 v table3 f8h 32 khz lposctr at 3.30 v table3 f9h 32 khz lposctr at 3.00 v table3 fah 32 khz lposctr at 2.85 v table3 fbh 32 khz lposctr at 2.70 v table 35. cpu clock config (cpuclkcr) [0x30] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved read/write ? ? ? ? ? ? ? ? default 0 0 0 0 0 0 0 0 bits 7:0 reserved note the cpu speed selection is config ured using the osc_cr0 register ( figure 11 on page 30). cyrf69103 document number: 001-07611 rev *i page 28 of 72 table 36. osc control 0 (osc_cr0) [0x1e0] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved no buzz sleep timer [1:0] cpu speed [2:0] read/write ? ? r/w r/w r/w r/w r/w r/w default 00001000 bits 7:6 reserved bit 5 no buzz during sleep (the sleep bit is set in the cpu_scr register? table 40 on page 32), the lvd and por detection circuit is turned on periodically to de tect any por and lvd events on the v cc pin (the sleep duty cycle bits in the eco_tr are used to control the duty cycle? table 44 on page 37). to facilitate the detection of por and lvd events, the no buzz bit is used to force the lvd and por detection circuit to be continuously enabled dur- ing sleep. this results in a faster response to an lv d or por event during sleep at the expense of a slightly higher than average sleep current. obtaining the absolute lowest power usage in sleep mode requires the no buzz bit be clear 0 = the lvd and por detection circuit is turned on periodically as configured in the sleep duty cycle. 1 = the sleep duty cycle value is overridden. the lvd and por detection circuit is always enabled. note the periodic sleep duty cycle enabling is independent with the sleep interval shown in the following sleep [1:0] bits. bits 4:3 sleep timer [1:0] note sleep intervals are approximate bits 2:0 cpu speed [2:0] the cyrf69103 may operate over a range of cpu clock speeds. the reset value for the cpu speed bits is zero. therefore, the def ault cpu speed is 3 mhz . sleep timer [1:0] sleep timer clock frequency (nominal) sleep period (nominal) watchdog period (nominal) 00 512 hz 1.95 ms 6 ms 01 64 hz 15.6 ms 47 ms 10 8 hz 125 ms 375 ms 11 1 hz 1 sec 3 sec cpu speed [2:0] cpu when internal oscillator is selected 000 3 mhz (default) 001 6 mhz 010 12 mhz 011 reserved 100 1.5 mhz 101 750 khz 110 187 khz 111 reserved cyrf69103 document number: 001-07611 rev *i page 29 of 72 interval timer clock (itmrclk) the interval timer clock (itmrclk) can be sourced from the internal 24 mhz oscillator, internal 32 khz low power oscillator, or timer capture clock. a programmab le prescaler of 1, 2, 3, or 4 then divides the selected sour ce. the 12-bit programmable interval timer is a simple down counter with a programmable reload value. it provides a 1 ? s resolution by default. when the down counter reaches zero, the next clock is spent reloading. the reload value can be read and written while the counter is running, but care must be taken to ensure that the counter does not unintentionally reload while the 12-bit reload value is only partially stored ? for example, between the two writes of the 12-bit value. the programmable interval timer generates interrupt to the cpu on each reload. the parameters to be set appears on the device editor view of psoc designer after you place the cyrf69103 timer user module. the parameters are pitimer_source and pitimer_divider. the pitimer_sour ce is the clock to the timer and the pitimer_divider is the value the clock is divided by. the interval register (pitmr) hol ds the value that is loaded into the pit counter on terminal count. the pit counter is a down counter. the programmable interval timer resolution is configurable. for example: tcapclk divide by x of cpu clock (for example tcapclk divide by 2 of a 24 mhz cpu clock gives a frequency of 12 mhz) itmrclk divide by x of tcapclk (for example, itmrclk divide by 3 of tcapclk is 4 mhz so resolution is 0.25 ? s). timer capture clock (tcapclk) the timer capture clock (tcapclk) can be sourced from the internal 24 mhz oscillator or the internal 32 khz low power oscillator. a programmable prescaler of 2, 4, 6, or 8 then divides the selected source. table 37. timer clock conf ig (tmrclkcr) [0x31] [r/w] bit # 7 6 5 4 3 2 1 0 field tcapclk divider tcapclk select itmrclk divider itmrclk select read/write r/w r/w r/w r/w r/w r/w r/w r/w default 1 0 0 0 1 1 1 1 bits 7:6 tcapclk divider [1:0] tcapclk divider controls the tcapclk divisor. 0 0 = divider value 2 0 1 = divider value 4 1 0 = divider value 6 1 1 = divider value 8 bits 5:4 tcapclk select the tcapclk select field contro ls the source of the tcapclk. 0 0 = internal 24 mhz oscillator 0 1 =reserved 1 0 = internal 32 khz low power oscillator 1 1 = tcapclk disabled note the 1024 ? s interval timer is based on the assumption that tcapclk is running at 4 mhz. changes in tcapclk frequency cause a corresponding change in the 1024 ? s interval timer frequency. bits 3:2 itmrclk divider itmrclk divider controls the itmrclk divisor 0 0 = divider value of 1 0 1 = divider value of 2 1 0 = divider value of 3 1 1 = divider value of 4 bits 1:0 itmrclk select 0 0 = internal 24 mhz oscillator 0 1 = reserved 1 0 = internal 32 khz low power oscillator 1 1 = tcapclk note changing the source of tmrclk requires t hat both the source and destination clo cks be running. attempting to change the clock source away from tcapclk after th at clock has been stopped is not successful. cyrf69103 document number: 001-07611 rev *i page 30 of 72 figure 11. programmable interval timer block diagram internal clock trim system clock clock timer configuration status and control 12-bit reload value 12-bit down counter 12-bit reload counter interrupt c ontroller table 38. iosc trim (iosctr) [0x34] [r/w] bit # 7 6 5 4 3 2 1 0 field foffset[2:0] gain[4:0] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 d d d d d the iosc calibrate register is used to calibrate the internal oscillator. the rese t value is undefined but during boot the srom writes a calibration valu e that is determined during manufacturing test. th e ?d? indicates that the default value is trimmed to 24 mhz at 3.30v at power on. bits 7:5 foffset [2:0] this value is used to trim the frequency of the internal oscillator. these bits are not used in factory calibration and are zero. setting each of these bits causes th e appropriate fine offset in oscillator frequency: foffset bit 0 = 7.5 khz foffset bit 1 = 15 khz foffset bit 2 = 30 khz bits 4:0 gain [4:0] the effective frequency change of the of fset input is controlled through the ga in input. a lower value of the gain setting increases the gain of t he offset input. this value sets the size of each offset step for the internal oscilla- tor. nominal gain change (khz/offsetstep) at each bit, typical conditions (24 mhz operation): gain bit 0 = ?1.5 khz gain bit 1 = ?3.0 khz gain bit 2 = ?6 khz gain bit 4 = ?24 khz cyrf69103 document number: 001-07611 rev *i page 31 of 72 lposc trim cpu clock during sleep mode when the cpu enters sleep mode, the oscillat or is stopped. when the cpu comes out of sleep mode it is running on the internal oscillator. the internal oscillator recovery time is thr ee clock cycles of the internal 32 khz low power oscillator. table 39. lposc trim (lposctr) [0x36] [r/w] bit # 7 6 5 4 3 2 1 0 field 32 khz low power reserved 32 khz bias trim [1:0] 32 khz freq trim [3:0] read/write r/w ? r/w r/w r/w r/w r/w r/w default 0 ? d d dd d d this register is used to calibrate the 32 khz low speed o scillator. the reset value is undefined but during boot the srom writes a calibration value that is determined during manufacturing test. this is the meaning of ?d? in the default field. the t rim value can be adjusted vs. voltage as noted in table 35 on page 27. bit 7 32 khz low power 0 = the 32 khz low speed oscillator operates in normal mode. 1 = the 32 khz low speed oscillator operates in a low power mode. the oscillator continues to function nor- mally but with reduced accuracy. bit 6 reserved bits [5:4] 32 khz bias trim [1:0] these bits control the bias current of the low power oscillator. 0 0 = mid bias 0 1 = high bias 1 0 = reserved 1 1 = reserved important note do not program the 32 khz bias trim [1:0] field with th e reserved 10b value as the oscillator does not oscillate at all corner conditi ons with this setting. bits 3:0 32 khz freq trim [3:0] these bits are used to trim the fr equency of the low power oscillator. cyrf69103 document number: 001-07611 rev *i page 32 of 72 reset the microcontroller supports two types of resets: power on reset (por) and watchdog reset (wdr). when reset is initiated, all registers are restored to their defaul t states and all interrupts are disabled. the occurrence of a reset is recorded in the system status and control register (cpu_scr). bits within this register record the occurrence of por and wdr reset respectively. the firmware can interrogate these bits to determine the cause of a reset. the microcontroller resumes execution from flash address 0x0000 after a reset. the internal clocking mode is active after a res et, until changed by user firmware. note the cpu clock defaults to 3 mhz (internal 24 mhz oscillator di vide-by-8 mode) at por to guar antee operation at the low v cc that might be present du ring the supply ramp. table 40. system status and control register (cpu_scr) [0xff] [r/w] bit # 7 6 5 4 3 2 1 0 field gies reserved wdrs pors sleep reserved reserved stop read/write r ? r/c [3] r/c [3] r/w ? ? r/w default 0 0 0 1 01 0 0 the bits of the cpu_scr register are used to convey stat us and control of events for various functions of a cyrf69103 device. bit 7 gies the global interrupt enable status bit is a read-only status bit and its use is discouraged. the gies bit is a legacy bit, which was used to provide the ability to re ad the gie bit of the cpu_f register. however, the cpu_f register is now readable. when this bit is set, it indicates that the gie bit in the cpu_f register is also set which, in turn, indicates that the microprocessor services interrupts: 0 = global interrupts disabled 1 = global interrupt enabled bit 6 reserved bit 5 wdrs the wdrs bit is set by the cpu to indicate that a wdr event has occurred. the user can read this bit to determine the type of reset that has occurred. the user can clear but not set this bit: 0 = no wdr 1 = a wdr event has occurred bit 4 pors the pors bit is set by the cpu to indicate that a po r event has occurred. the user can read this bit to determine the type of reset that has occurred. the user can clear but not set this bit: 0 = no por 1 = a por event has occurred (note that wdr event s do not occur until this bit is cleared). bit 3 sleep set by the user to enable cpu sleep state. cpu remains in sleep mode until any interrupt is pending. the sleep bit is covered in more detail in the section sleep mode on page 33. 0 = normal operation 1 = sleep bits 2:1 reserved bit 0 stop this bit is set by the user to halt the cpu. the cpu re mains halted until a reset (wdr, por, or external reset) has taken place. if an application wants to stop code execut ion until a reset, the preferred method is to use the halt instruction rather than writing to this bit. 0 = normal cpu operation 1 = cpu is halted (not recommended) note 3. c = clear. this bit can only be cleared by the user and cannot be set by firmware. cyrf69103 document number: 001-07611 rev *i page 33 of 72 power on reset por occurs every time the power to the device is switched on. por is released when the supply is typically 2.6 v for the upward supply transition, with typically 50 mv of hysteresis during the power on transient. bit 4 of the system status and control register (cpu_scr) is set to record this event (the register contents are set to 00010000 by the por). after a por, the microprocessor is held off for approximately 20 ms for the v cc supply to stabilize before executing the first instruction at address 0x00 in the flash. if the v cc voltage drops below the por downward supply trip point, por is reasserted. the v cc supply needs to ramp linearly from 0 to v cc in 0 to 200 ms. important the pors status bit is set at por and can only be cleared by the user, and cannot be set by firmware. watchdog timer reset the user has the option to enable the wdt. the wdt is enabled by clearing the pors bit. when the pors bit is cleared, the wdt cannot be disabled. the only exception to this is if a por event takes place, which disables the wdt. the sleep timer is used to generate the sleep time period and the watchdog time period. the sleep timer uses the internal 32 khz low power oscillator system clock to produce the sleep time period. the user can program the sleep time period using the sleep timer bits of the osc_cr0 register ( table 36 on page 28). when the sleep time elapses (sleep timer overflows), an interrupt to the sleep timer interrupt vector is generated. the watchdog timer period is automatically set to be three counts of the sleep timer overflows. this represents between two and three sleep intervals depending on the count in the sleep timer at the previous wdt clear. when this timer reaches three, a wdr is generated. the user can either clear the wdt, or the wdt and the sleep timer. whenever the user writes to the reset wdt register (res_wdt), the wdt is cleared. if the data that is written is the hex value 0x38, the sleep timer is also cleared at the same time. sleep mode the cpu can only be put to sleep by the firmware. this is accomplished by setting the sleep bit in the system status and control register (cpu_scr). this stops the cpu from executing instructions, and the cpu remains asleep until an interrupt comes pending, or there is a reset event (either a power on reset, or a watchdog timer reset). the low voltage detection circuit (lvd) drops into fully functional power reduced states, and the latency for the lvd is increased. the actual latency can be tra ded against power consumption by changing the sleep duty cycle field of the eco_tr register. the internal 32 khz low speed oscillator remains running. before entering suspend mode, firmware can optionally configure the 32 khz low speed oscillator to operate in a low power mode to help reduce the overall power consumption (using the 32 khz low power bit, ta b l e 3 9 ). this helps save approximately 5 ? a; however, the trade off is that the 32 khz low speed oscillator be less accurate (?53.12% to +56.25% deviation). all interrupts remain active. only the occurrence of an interrupt wakes the part from sleep. the st op bit in the system status and control register (cpu_scr) must be cleared for a part to resume out of sleep. the global interrupt enable bit of the cpu flags register (cpu_f) does not have any effect. any unmasked interrupt wakes the system up. as a result, any interrupts not intended for waking must be disabled through the interrupt mask registers. when the cpu enters sleep mode, the internal oscillator is stopped. when the cpu comes out of sleep mode, it is running on the internal oscillator. the internal oscillator recovery time is three clock cycles of the internal 32 khz low power oscillator. on exiting sleep mode, when the clock is stable and the delay time has expired, the instruction immediately following the sleep instruction is executed before th e interrupt service routine (if enabled). the sleep interrupt allows the microcontroller to wake up period- ically and poll system components while maintaining very low average power consumption. the sleep interrupt may also be used to provide periodic interrupts during non sleep modes. sleep sequence the sleep bit is an input into the sleep logic circuit. this circuit is designed to sequence the device into and out of the hardware sleep state. the hardware sequence to put the device to sleep is shown in figure 12 on page 34 and is defined as follows. 1. firmware sets the sleep bit in the cpu_scr0 register. the bus request (brq) signal to the cpu is immediately asserted. this is a request by the system to halt cpu operation at an instruction boundary. the cpu samples brq on the positive edge of cpuclk. 2. due to the specific timing of the register write, the cpu issues a bus request acknowledge (bra) on the following positive edge of the cpu clock. the sleep logic waits for the following negative edge of the cpu clock and then asserts a system-wide power down (pd) signal. in figure 12 on page 34 the cpu is halted and the system-wide power down signal is asserted. table 41. reset watchdog timer (reswdt) [0xe3] [w] bit # 7 6 5 4 3 2 1 0 field reset watchdog timer [7:0] read/write w w w w ww w w default 0 0 0 0 00 0 0 any write to this register clears the watchdog ti mer, a write of 0x38 also clears the sleep timer. bits 7:0 reset watchdog timer [7:0] cyrf69103 document number: 001-07611 rev *i page 34 of 72 3. the system-wide pd (power dow n) signal controls several major circuit blocks: the flas h memory module, the internal 24 mhz oscillator, the eftb filter and the bandgap voltage reference. these circuits transition into a zero power state. the only operational circuits on chip are the low power oscillator, the bandgap refresh circuit, and the supply voltage monitor (por/lvd) circuit. low power in sleep mode to achieve the lowest possible power consumption during suspend or sleep, the following conditions are observed in addition to considerations for the sleep timer: all gpios are set to outputs and driven low clear p11cr[0], p10cr[0] set p10cr[1] to avoid current consumption make sure itmrclk and tcpclk are not sourced by either low power 32 khz oscillator or 24 mhz crystal-less oscillator. all the other blocks go to the power down mode automatically on suspend. the following steps are user configurable and help in reducing the average suspend mode power consumption: 1. configure the power supply monitor at a large regular intervals, control register bi ts are 1,eb[7:6] (power system sleep duty cycle pssdc[1:0]). 2. configure the low power oscillator into low power mode, control register bit is lopsctr[7]. figure 12. sleep timing wakeup sequence when asleep, the only event that can wake the system up is an interrupt. the global interrupt enable of the cpu flag register does not need to be set. any unmasked interrupt wakes the system up. it is optio nal for the cpu to actu ally take the interrupt after the wakeup sequence. the wakeup sequence is synchronized to the 32 khz clock. this is done to sequence a startup delay and enable the flash memory module enough time to power up before the cpu asserts the first read access. another reason for the delay is to enable the oscillator, bandgap, and lvd/por circuits time to se ttle before actually being used in the system. as shown in figure 13 on page 35, the wakeup sequence is as follows: 1. the wakeup interrupt occurs and is synchronized by the negative edge of the 32 khz clock. 2. at the following positive edge of the 32 khz clock, the system-wide pd signal is negated. the flash memory module, internal oscillator, eftb, and bandgap circuit are all powered up to a normal operating state. 3. at the following positive edge of the 32 khz clock, the current values for the precision por and lvd have settled and are sampled. 4. at the following negative edge of the 32 khz clock (after about 15 s nominal), the brq signal is negated by the sleep logic circuit. on the following cpuclk, bra is negated by the cpu and instruction execution resumes. note that in figure 13 on page 35 fixed function blocks, such as flash, internal oscil- lator, eftb, and bandgap, have about 15 s start up. the wakeup times (interrupt to cpu operational) ranges from 75 s to 105 s. firmware write to scr sleep bit causes an immediate brq iow sleep brq pd bra cpuclk cpu captures brq on next cpuclk edge cpu responds with a bra on the falling edge of cpuclk, pd is asserted. the 24/48 mhz system clock is halted; the flash and bandgap are powered down cyrf69103 document number: 001-07611 rev *i page 35 of 72 figure 13. wakeup timing int sleep pd bandgap clk32k sample sample lvd/por cpuclk/ 24mhz bra brq enable cpu (not to scale) sleep timer or gpio interrupt occurs interrupt is double sampled by 32k clock and pd is negated to system cpu is restarted after 90 ms (nominal) cyrf69103 document number: 001-07611 rev *i page 36 of 72 low voltage detect control table 42. low voltage control register (lvdcr) [0x1e3] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved porlev[1:0] reserved vm[2:0] read/write ? ? r/w r/w ?r/w r/w r/w default 0 0 0 0 00 0 0 this register controls the configuration of the power on reset/low voltage detection circuit. this register can only be accesse d in the second bank of i/o space. this requires setting the xio bit in the cpu flags register. bits 7:6 reserved bits 5:4 porlev[1:0] this field controls the level below which the precis ion power on reset (ppor) detector generates a reset 0 0 = 2.7 v range (trip near 2.6 v) 0 1 = 3 v range (trip near 2.9 v) 1 0 = reserved 1 1 = ppor does not generate a reset, but values re ad from the voltage monitor comparators register ( ta b l e 43 on page 37) give the internal ppor comparator st ate with trip point set to the 3 v range setting. bit 3 reserved bits 2:0 vm[2:0] this field controls the level below which the low voltage-detect trips?possibly generating an interrupt and the level at which the flash is enabled for operation. vm[2:0] lvd trip point typ. (v) 000 2.7 001 2.92 010 3.02 011 3.13 100 101 110 111 cyrf69103 document number: 001-07611 rev *i page 37 of 72 por compare state eco trim register table 43. voltage monitor comparators register (vltcmp) [0x1e4] [r] bit # 7 6 5 4 3 2 1 0 field reserved lvd ppor read/write ? ? ? ? ?? r r default 0 0 0 0 00 0 0 this read-only register allows reading the current state of the low voltage detection and precision-power-on-reset comparators: bits 7:2 reserved bit 1 lvd this bit is set to indicate that the low voltage detect comparator has tripped, indica ting that the supply voltage has gone below the trip point set by vm[2:0] (see table 42 on page 36). 0 = no low voltage detect event 1 = a low voltage detect has tripped bit 0 ppor this bit is set to indicate that the precision-power-on -reset comparator has tripped, indicating that the supply voltage is below the trip point set by porlev[1:0]: 0 = no precision-power-on-reset event 1 = a precision-power-on-reset event has tripped note this register can only be accessed in the second bank of i/o space. this requires setting the xio bit in the cpu flags register table 44. eco (eco_tr) [0x1eb] [r/w] bit # 7 6 5 4 3 2 1 0 field sleep duty cycle [1:0] reserved read/write r/w r/w ? ? ? ? ? ? default 0 0 0 0 00 0 0 this register controls the ratios (in numbers of 32 khz clock pe riods) of ?on? time versus ?off? time for lvd and por detection circuit. bits 7:6 sleep duty cycle [1:0] 0 0 = 1/128 periods of the inter nal 32 khz low-speed oscillator 0 1 = 1/512 periods of the inter nal 32 khz low-speed oscillator 1 0 = 1/32 periods of the internal 32 khz low-speed oscillator 1 1 = 1/8 periods of the internal 32 khz low speed oscillator note this register can only be accessed in the second bank of i/o space. this requires setting the xio bit in the cpu flags register cyrf69103 document number: 001-07611 rev *i page 38 of 72 general purpose i/o ports the general purpose i/o ports are discussed in the following sections. port data registers table 45. p0 data register (p0data)[0x00] [r/w] bit # 7 6 5 4 3 2 1 0 field p0.7 reserved p0.4/in t2 p0.3/int1 reserved p0.1 reserved read/write r/w ? r/w r/w ? r/w ? default 0 ? ? 0 00 0 ? this register contains the data for port 0. writing to this register sets the bit values to be output on output enabled pins. r eading from this register returns the current state of the port 0 pins. bit 7 p0.7 data bits 6:5 reserved bits 4:3 p0.4?p0.3data/int2?int1 in addition to their use as the p0.4?p0. 3 gpios, these pins can also be used for the alternative functions as the interrupt pins (int1?int2). to configure the p0.4?p0. 3 pins, refer to the p0.3/int1?p0.4/int2 configuration register ( table 49 on page 40). bit 2 reserved bit 1 p0.1 data bit 0 reserved table 46. p1 data register (p1data) [0x01] [r/w] bit # 7 6 5 4 3 2 1 0 field p1.7 p1.6 p1.5/smosi p1.4/s clk p1.3/ssel p1.2 p1.1 p1.0 read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 0 0 0 ? this register contains the data for port 1. writing to this register sets the bit values to be output on output enabled pins. r eading from this register returns the current state of the port 1 pins. bits 7 p1.7 bits 6 p1.6 or alternate function of smosi in a 4-wire spi bits 5:3 p1.5?p1.3 data/3-wire spi pi ns (smiso/smosi, sclk, ssel) in addition to their use as the p1.6?p1.3 gpios, these pi ns can also be used for the alternative function as the spi interface pins. to configure th e p1.6?p1.3 pins, refer to the p1 .3?p1.6 configuration register ( ta b l e 5 4 on page 42) bits 2:1 p1.2?p1.1 bit 0 p1.0 table 47. p2 data register (p2data) [0x02] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved p2.1?p2.0 read/write ? r/w r/w default ? 00 this register contains the data for port 2. writing to this register sets the bit values to be output on output enabled pins. r eading from this register returns the current state of the port 2 pins. bits 7:2 p2 data [7:2] bits 1:0 p2 data [1:0] cyrf69103 document number: 001-07611 rev *i page 39 of 72 gpio port configuration all the gpio configuration regi sters have common configuration controls. the following are the bit definitions of the gpio configuration registers. by def ault all gpios are configured as inputs. to prevent the inputs from floating, the pull up resistors are enabled. firmware needs to configure each of the gpios before use. int enable when set, the int enable bit allows the gpio to generate interrupts. interrupt generate can occur regardless of whether the pin is configured for input or output. all interrupts are edge sensitive, however for any interr upt that is shared by multiple sources (that is, ports 2, 3, and 4) all inputs must be deasserted before a new interrupt can occur. when clear, the corresponding interrupt is disabled on the pin. it is possible to configure gpios as outputs, enable the interrupt on the pin and then to generate the interrupt by driving the appropriate pin state. this is us eful in test and may have value in applications. int act low when clear, the corresponding interrupt is active high. when set, the interrupt is active low. for p0.3?p0.4 int act low clear causes interrupts to be active on the rising edge. int act low set causes interrupts to be active on the falling edge. ttl thresh when set, the input has ttl threshold. when clear, the input has standard cmos threshold. important note the gpios default to cmos threshold. user?s firmware needs to configure the threshold to ttl mode if necessary. high sink when set, the output can sink up to 50 ma. when clear, the output can sink up to 8 ma. open drain when set, the output on the pin is determined by the port data register. if the corresponding bit in the port data register is set, the pin is in high impedance state. if the corresponding bit in the port data register is clear, the pin is driven low. when clear, the output is driven low or high. pull up enable when set the pin has a 7k pull up to v dd . when clear, the pull up is disabled. output enable when set, the output driv er of the pin is enabled. when clear, the output driver of the pin is disabled. for pins with shared functions there are some special cases. p0.0 (clkin) and p0.1 (clkout) can not be output enabled when the crystal oscillator is enabled. output enables for these pins are overridden by xosc enable. p1.3 (ssel), p1.4 (sclk), p1 .5 (smosi) and p1.6 (smiso) can be used for their dedicated functions or for gpio. to enable the pin for gpio use, clear the corresponding spi use bit or the output enable has no effect. spi use the p1.3 (ssel), p1.4 (scl k), p1.5 (smosi) and p1.6 (smiso) pins can be used for their dedicated functions or for gpio. to enable the pin for gpio, clear the corresponding spi use bit. the spi function controls the output enable for its dedicated function pins when their gpio enable bit is clear. table 48. p0.1 configuration (p01cr) [0x06] r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low ttl thresh high sink open drain pull up enable output enable read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 this register is used to configure p0.1 . in the cyrf69103, only 8 ma sink drive capability is available on this pin regardless of the setting of the high sink bit. if this pin is used as a general purpose output it draws current. this pin must be configured as an input to reduce current dra w. bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 see ttl thresh bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable cyrf69103 document number: 001-07611 rev *i page 40 of 72 bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 see ttl thresh bit 3 reserved bit 2 see open drain bit 1 see pull up enable bit 0 see output enable table 49. p0.3?p0.4 configuration (p03cr?p04cr) [0x08?0x09] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int act low ttl thresh reserved open drain pull up enable output enable read/write ? ? r/w r/w ?r/w r/w r/w default 0 0 0 0 00 0 0 these registers control the o peration of pins p0.3?p0.4 respectively. thes e pins are shared between the p0.3?p0.4 gpios and the int1?int2. the int1?int2 interrupts are different than all the other gpio interrupts. these pins are connected directly to the interrupt controller to provide three edge-sensitive interrupts with independent interrupt vectors. these inter rupts occur on a rising edge when int act low is clear and on a falling edge when int act low is set. these pins are enabled as interrupt sources in the inte rrupt controller registers ( table 75 on page 55 and table 73 on page 54). to use these pins as interrupt inputs, configure them as inputs by clearing the corresponding output enable. if the int1?int2 pins are configured as outputs with interru pts enabled, firmware can generate an interr upt by writing the appropriate value to the p0.3, and p0.4 data bits in the p0 data register. regardless of whether the pins are used as interrupt or gpio pins the int enable, int act low, ttl threshold, open drain, and pull up enable bits control the behavior of the pin. the p0.3/int1?p0.4/int2 pins are individually configured with the p03cr (0x08), and p04cr (0x09) respectively. note changing the state of the int act low bit can cause an unint entional interrupt to be gener ated. when configuring these interrupt sources, it is best to follow the following procedure: 1. disable interrupt source 2. configure interrupt source 3. clear any pending interrupts from the source 4. enable interrupt source table 50. p0.7 configuration (p07cr) [0x0c] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low ttl thresh reserved open drain pull up enable output enable read/write ?r/wr/wr/w?r/wr/wr/w default 00000000 t his register controls the operation of pin p0.7. cyrf69103 document number: 001-07611 rev *i page 41 of 72 bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 reserved bit 2 reserved bit 1 0 = disables the 5k ohm pull up resistors 1 = enables 5k ohm pull up resistors for both p1.0 and p1.1 (this is not compatible with usb) bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 reserved bit 2 see open drain bit 1 reserved bit 0 see output enable table 51. p1.0 configuration (p10cr) [0x0d] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low reserved reserved reserved 5k pullup enable output enable read/write r/w r/w r/w - - - r/w r/w default 00000000 this register controls the operation of the p1.0 pin. note the p1.0 is an open drain only output. it can actively drive a signal low, but cannot actively drive a signal high. bit 0 this bit enables the output on p1.0. this bit must be cleared in sleep mode. table 52. p1.1 configuration (p11cr) [0x0e] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low reserved open drain reserved output enable read/write ? r/w r/w ? ?r/w? r/w default 00000000 this register controls the operation of the p1.1 pin. the pull up resistor on this pin is enabled by the p10cr register. note there is no 2 ma sourcing capability on this pin. the pin can only sink 5 ma at v ol3 section. cyrf69103 document number: 001-07611 rev *i page 42 of 72 table 53. p1.2 configuration (p12cr) [0x0f] [r/w] bit # 7 6 5 4 3 2 1 0 field clk output int enable int act low ttl threshold reserved open drain pull up enable output enable read/write r/w r/w r/w r/w ?r/w r/w r/w default 0 0 0 0 00 0 0 this register controls the operation of the p1.2. bit 7 clk output 0 = the internally selected clock is not sent out onto p1.2 pin. 1 = when clk output is set, the internally selected clock is sent out onto p1.2 pin. bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable table 54. p1.3 configuration (p13cr) [0x10] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low reserved high sink open drain pull up enable output enable read/write ? r/w r/w ?r/wr/w r/w r/w default 0 0 0 000 0 0 this register controls the operation of the p1.3 pin. the p1.3 gpio?s threshold is always set to ttl. when the spi hardware is enabled, the output enable and output st ate of the pin is controlled by the spi circuitry. when the spi hardware is disabled, the pin is controlled by the output enable bit and the corresponding bit in the p1 data register. regardless of whether the pin is used as an spi or gpio pin the int enable, int act low, high sink, open drain, and pull up enable control the behavior of the pin. 50 ma sink drive capability is available. bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable cyrf69103 document number: 001-07611 rev *i page 43 of 72 table 55. p1.4?p1.6 configuration (p14cr?p16cr) [0x11?0x13] [r/w] bit # 7 6 5 4 3 2 1 0 field spi use int enable int act low reserved high sink open drain pull up enable output enable read/write r/w r/w r/w ?r/wr/w r/w r/w default 0 0 0 000 0 0 these registers control the operation of pins p1.4?p1.6, respectively. the p1.4?p1.6 gpio?s threshold is always set to ttl. when the spi hardware is enabled, pins that are configured as spi use have their output enable and output state controlled by the spi circuitry. when the spi hardware is disabled or a pi n has its spi use bit clear, the pin is controlled by the output enable bit and the corresponding bit in the p1 data register. regardless of whether any pin is used as an spi or gpio pin the int enable, int act low, high sink, open drain, and pull up enable control the behavior of the pin. bit 7 spi use 0 = disable the spi alternate func tion. the pin is used as a gpio 1 = enable the spi function. the spi circ uitry controls the output of the pin bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable note for comm modes 01 or 10 (spi master or spi slave, see table 59 on page 46 ) when configured for spi (spi use = 1 and comm modes [1:0] = spi master or spi slave mode), the input/output direction of pins p1.3, p1.5, and p1.6 is set aut omatically by the spi logic. however, pin p1.4's input/output direction is not automatically set; it must be explicitly set by firmware. for spi master m ode, pin p1.4 must be configured as an output; for spi slave mode, pin p1.4 must be configured as an input. table 56. p1.7 configuration (p17cr) [0x14] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low reserved high sink open drain pull up enable output enable read/write ? r/w r/w ? r/w r/w r/w r/w default 00000000 this register controls the operation of pin p1.7. 50 ma sink drive capability is available. the p1.7 gpio?s threshold is always set to ttl. bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 reserved bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable cyrf69103 document number: 001-07611 rev *i page 44 of 72 gpio configurations for low power mode to ensure low power mode, unbonded gpio pins in cyrf69103 must be placed in a non-floating state. the following assembly code snippet shows how this is achieved. this snippet c an be added as a part of the initialization routine. //code snippet for addressing unbonded gpios mov a, 01h mov reg[1fh],a mov a, 01h mov reg[16h],a // port3 configuration register - enable output mov a, 00h mov reg[03h],a // asserting p3.0 to p3.7 outputs to '0' //port 2 configurations mov a,01h mov reg[15h],a //port 2 configuration register -enable output mov a,00h mov reg[02h],a //asserting p2.0 to p2.7 outputs to ?0? mov a, 01h mov reg[05h],a // port0.0 configuration register - enable output mov reg[07h],a // port0.2 configuration register - enable output mov reg[0ah],a // port0.5 configuration register - enable output mov reg[0bh],a // port0.6 configuration register - enable output mov a,reg[00h] mov a,00h and a,9ah mov reg[00h], a // asserting outputs '0' to pins in port 1 // note: the code fragment in italics is to be used only if your application configures p2.0 and p2.1 as push-pull outputs. when writing to port 0, to access gpios p0.1,3,4,7, ma sk bits 0,2,5,6. failing to do so voids the low power. table 57. p2 configuration (p2cr) [0x15] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved int enable int act low ttl thresh high sink open drain pull up enable output enable read/write ? r/w r/w r/w r/w r/w r/w r/w default 00000000 this register controls the operation of pins p2.0?p2.1. bit 7 reserved bit 6 see int enable bit 5 see int act low bit 4 see ttl thresh bit 3 see high sink bit 2 see open drain bit 1 see pull up enable bit 0 see output enable cyrf69103 document number: 001-07611 rev *i page 45 of 72 serial peripheral interface (spi) the spi master/slave interface core logic ru ns on the spi clock domain. the spi clock is a divider off of the cpuclk when in ma ster mode. spi is a four-pin serial interface comprised of a clock, an enable, and two data pins. figure 14. spi block diagram spi state machine ss_n data (8 bit) load empty data (8 bit) load full sclk output enable slave select output enable master in, slave out oe master out, slave in, oe shift buffer input shift buffer output shift buffer sck clock generation sck clock select sck clock phase/polarity select register block sck speed sel master/slave sel sck polarity sck phase little endian sel miso/mosi crossbar gpio block ss_n le_sel sck le_sel sck_oe ss_n_oe miso_oe mosi_oe sck sck_oe ss_n_oe sck ss_n master/slave set miso mosi miso_oe mosi_oe cyrf69103 document number: 001-07611 rev *i page 46 of 72 spi data register when an interrupt occurs to indicate to firmware that an byte of receive data is available, or the transmitter holding register is empty, firmware has 7 spi clocks to manage the buffers ? to empty the receiver buffer, or to refill the transmit holding register. fai lure to meet this timing requirement results in incorrect data transfer. spi configure register table 58. spi data register (spidata) [0x3c] [r/w] bit # 7 6 5 4 3 2 1 0 field spidata[7:0] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 when read, this register returns the cont ents of the receive buffer. when written, it loads the transmit holding register. bits 7:0 spi data [7:0] table 59. spi configure register (spicr) [0x3d] [r/w] bit # 7 6 5 4 3 2 1 0 field swap lsb first comm mode cpol cpha sclk select read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 bit 7 swap 0 = swap function disabled. 1 = the spi block swaps its use of smosi and smiso. am ong other things, this can be useful in implementing single wire spi-like communications. bit 6 lsb first 0 = the spi transmits and receives t he msb (most significant bit) first. 1 = the spi transmits and receives the lsb (least significant bit) first. bits 5:4 comm mode [1:0] 0 0: all spi communication disabled. 0 1: spi master mode 1 0: spi slave mode 1 1: reserved bit 3 cpol this bit controls the spi clock (sclk) idle polarity. 0 = sclk idles low 1 = sclk idles high bit 2 cpha the clock phase bit controls the phase of the clock on which data is sampled. table 60 on page 47 shows the timing for the various combinations of lsb first, cpol, and cpha. bits 1:0 sclk select this field selects the speed of the master sclk. when in master mode, sclk is gener ated by dividing the base cpuclk. important note for comm modes 01b or 10b (spi master or spi slave): when configured for spi, (spi use = 1 ? table 55 on page 43), the input/output direction of pins p1.3, p1.5, and p1.6 is set automatically by the spi logic. however, pi n p1.4's input/output directio n is not automatically set; it must be explicitly set by firmware. for spi master mode, pin p1.4 must be configured as an output; for spi slave mode, pin p1.4 must be configured as an input. cyrf69103 document number: 001-07611 rev *i page 47 of 72 table 60. spi mode timing vs. lsb first, cpol and cpha lsb first cpha cpol diagram 000 001 010 011 100 101 110 111 sclk ssel data x x msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel x x data msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel x x data msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel data x x msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel data x x msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel x x data msb bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb sclk ssel x x data msb bit 2bit 3bit 4bit 5bit 6bit 7 lsb sclk ssel data x msb x bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 lsb cyrf69103 document number: 001-07611 rev *i page 48 of 72 spi interface pins the spi interface between the ra dio function and mcu function uses pins p1.3?p1.5 and optio nally p1.6. these pins are configured using the p1.3 and p1.4?p1.6 configuration. timer registers all timer functions of the cyrf69103 are provided by a single timer block. the timer block is asynchronous from the cpu clock. the 16-bit free running counter is used as the time-base for timer captures and can also be used as a general time-base by software. registers free running counter the 16-bit free running counter is clocked by a 4 or 6 mhz source. it can be read in software for use as a general purpose time base. when the low order by te is read, the high order byte is registered. reading the high order byte reads this register allowing the cpu to read the 16-b it value atomically (loads all bits at one time). the free running timer generates an interrupt at 1024 ? s rate. it can also generate an interrupt when the free running counter overflow occurs?every 16.384 ms. this allows extending the length of the timer in software. figure 15. 16-bit free running counter block diagram table 61. spi sclk frequency sclk select cpuclk divisor sclk frequency when cpuclk = 12 mhz 00 6 2 mhz 01 12 1 mhz 10 48 250 khz 11 96 125 khz timer capture clock 16-bit free running counter overflow interrupt 1024-s timer interrupt table 62. free running timer low order byte (frtmrl) [0x20] [r/w] bit # 7 6 5 4 3 2 1 0 field free running timer [7:0] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 bits 7:0 free running timer [7:0] this register holds the low order byte of the 16-bit free running timer. reading this re gister causes the high order byte to be moved into a holding register allowing an automatic read of all 16 bits simultaneously. for reads, the actual read occurs in the cycle when the low order is read. for writes the actual time the write occurs is the cycle when the high order is written. when reading the free running timer, the low order byte must be read first and the high order second. when writing, the low order byte must be written fi rst then the high order byte. cyrf69103 document number: 001-07611 rev *i page 49 of 72 table 63. free running timer high-order byte (frtmrh) [0x21] [r/w] bit # 7 6 5 4 3 2 1 0 field free running timer [15:8] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 bits 7:0 free running timer [15:8] when reading the free running timer, the low order byte must be read first and the high order second. when writing, the low order byte must be written fi rst then the high order byte. table 64. programmable interval timer low (pitmrl) [0x26] [r] bit # 7 6 5 4 3 2 1 0 field prog interval timer [7:0] read/write r r r r rr r r default 0 0 0 0 00 0 0 bits 7:0 prog interval timer [7:0] this register holds the low order byte of the 12-bit programmable interval timer. reading this r egister causes the high order byte to be moved into a holding register allowing an automatic read of all 12 bits simultaneously. table 65. programmable interval timer high (pitmrh) [0x27] [r] bit # 7 6 5 4 3 2 1 0 field reserved prog interval timer [11:8] read/write -- -- -- -- rr r r default 0 0 0 0 00 0 0 bits 7:4 reserved bits 3:0 prog internal timer [11:8] this register holds the high order nibble of the 12-bit programmable interval timer. reading this register returns the high ord er nibble of the 12-bit timer at the instant that the low order byte was last read. table 66. programmable interval reload low (pirl) [0x28] [r/w] bit # 7 6 5 4 3 2 1 0 field prog interval [7:0] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 bits 7:0 prog interval [7:0] this register holds the lower 8 bits of the timer. while writi ng into the 12-bit reload register , write lower byte first then t he higher nibble. cyrf69103 document number: 001-07611 rev *i page 50 of 72 figure 16. 16-bit free running counter loading timing diagram table 67. programmable interval reload high (pirh) [0x29] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved prog interval[11:8] read/write -- -- -- -- r/w r/w r/w r/w default 0 0 0 0 00 0 0 bits [7:4] reserved bits 3:0 prog interval [11:8] this register holds the higher 4 bits of the timer. while writ ing into the 12-bit reload regi ster, write lower byte first then the higher nibble. clk_sys write valid addr write data frt reload ready clk timer 12b prog timer 12b reload interrupt capture timer clk 16b free running counter load 16b free running counter 00a0 00a1 00a2 00a3 00a4 00a5 00a6 00a7 00a8 00a9 00ab 00ac 00ad 00ae 00af 00b0 00b1 00b2 acbe acbf acc0 16-bit free running counter loading timing 12-bit programmable timer load timing cyrf69103 document number: 001-07611 rev *i page 51 of 72 figure 17. memory mapped regi sters read/write timing diagram interrupt controller the interrupt controller and its associated registers allow the user?s code to respond to an interrupt from almost every functional block in the cyrf69103 devices. the registers associated with the interrupt controller allow interrupts to be disabled either globally or individually. the registers also provide a mechanism by which a user may clear all pending and posted interrupts, or clear individual posted or pending interrupts. the following table lists all interrupts and the priorities that are available in the cyrf69103. architectural description an interrupt is posted when its interrupt conditions occur. this results in the flip-flop in figure 18 on page 52 clocking in a ?1?. the interrupt remains posted until the interrupt is taken or until it is cleared by writing to the appropriate int_clrx register. a posted interrupt is not pending unless it is enabled by setting its interrupt mask bit (in the appr opriate int_mskx register). all pending interrupts are processed by the priority encoder to determine the highest priority interrupt which is taken by the m8c if the global interrupt enable bit is set in the cpu_f register. disabling an interrupt by clearing its interrupt mask bit (in the int_mskx register) does not clear a posted interrupt, nor does it prevent an interrupt from being posted. it simply prevents a posted interrupt from becoming pending. nested interrupts can be accomplished by reenabling interrupts inside an interrupt service routine. to do this, set the ie bit in the flag register. a block diagram of the cyrf69103 interrupt controller is shown in figure 18 on page 52. memory mapped registers read/write timing diagram clk_sys rd_wrn valid addr rdata wdata table 68. interrupt priorities, address, name interrupt priority interrupt address name 0 0000h reset 1 0004h por/lvd 2 0008h reserved 3 000ch spi transmitter empty 4 0010h spi receiver full 5 0014h gpio port 0 6 0018h gpio port 1 7 001ch int1 8 0020h reserved 9 0024h reserved 10 0028h reserved 11 002ch reserved 12 0030h reserved 13 0034h 1 ms interval timer 14 0038h programmable interval timer 15 003ch reserved 16 0040h reserved 17 0044h 16-bit free running timer wrap 18 0048h int2 19 004ch reserved 20 0050h gpio port 2 21 0054h reserved 22 0058h reserved 23 005ch reserved 24 0060h reserved 25 0064h sleep timer table 68. interrupt priorities, address, name (continued) interrupt priority interrupt address name cyrf69103 document number: 001-07611 rev *i page 52 of 72 figure 18. interrupt controller block diagram interrupt processing the sequence of events that occur during interrupt processing is as follows: 1. an interrupt becomes active, either because: a. the interrupt condition occurs (for example, a timer expires). b. a previously posted interrupt is enabled through an update of an interrupt mask register. c. an interrupt is pending and gie is set from 0 to 1 in the cpu flag register. 2. the current executing instruction finishes. 3. the internal interrupt is dispatched, taking 13 cycles. during this time, the following actions occur: a. the msb and lsb of program counter and flag registers (cpu_pc and cpu_f) are stored onto the program stack by an automatic call instruction (13 cycles) generated during the interrupt acknowledge process. b. the pch, pcl, and flag register (cpu_f) are stored onto the program stack (in that order) by an automatic call instruction (13 cycles) gen erated during the interrupt acknowledge process. c. the cpu_f register is then cleared. because this clears the gie bit to 0, additional interrupts are temporarily disabled. d. the pch (pc[15:8]) is cleared to zero. e. the interrupt vector is read from the interrupt controller and its value placed into pcl (pc[7:0]). this sets the program counter to point to the appropriate address in the interrupt table (for example, 0004h for the por/lvd interrupt). 4. program execution vectors to the interrupt table. typically, a ljmp instruction in the interrupt table sends execution to the user's interrupt service rout ine (isr) for this interrupt. 5. the isr executes. note that interrupts are disabled because gie = 0. in the isr, interrupts can be re-enabled if desired by setting gie = 1 (care must be taken to avoid stack overflow). 6. the isr ends with a reti instruction which restores the program counter and flag registers (cpu_pc and cpu_f). the restored flag register re-e nables interrupts because gie = 1 again. 7. execution resumes at the next instruction, after the one that occurred before the interrupt. however, if there are more pending interrupts, the subsequent interrupts are processed before the next normal program instruction. interrupt latency the time between the assertion of an enabled interrupt and the start of its isr can be calculated from the following equation. latency = time for current instruct ion to finish + time for internal interrupt routine to execute + time for ljmp instruction in interrupt table to execute. for example, if the 5-cycle jmp in struction is executing when an interrupt becomes active, the total number of cpu clock cycles before the isr begins is as follows: (1 to 5 cycles for jmp to finish) + (13 cycles for interrupt routine) + (7 cycles for ljmp) = 21 to 25 cycles. in the following example, at 12 mhz, 25 clock cycles take 2.08 s. interrupt registers the interrupt registers are discussed it the following sections. interrupt clear register the interrupt clear registers (int_clrx) are used to enable the individual interrupt sources? ability to clear posted interrupts. when an int_clrx register is read, any bits that are set indicates an interrupt has been posted for that hardware resource. therefore, reading thes e registers gives the user the ability to determine all posted interrupts. interrupt source (timer, gpio, etc.) interrupt tak en or posted interrupt pending interrupt gie interrupt vector mask bit setting d r q 1 priority encoder m8c c o r e interrupt request ... int_mskx int_clrx write cpu_f[0] ... cyrf69103 document number: 001-07611 rev *i page 53 of 72 interrupt mask registers the interrupt mask registers (int_mskx) are used to enable the individual interrupt sources? ability to create pending interrup ts. there are four interrupt mask registers (int_msk0, int_msk1, int_msk2, and int_msk3) that may be referred to in general as int_mskx. if cleared, each bit in an int_mskx register prevents a posted interrupt from becoming a pending interrupt (input to the priority encoder). however, an interrupt can still post even if its mask bit is zero. all int_mskx bits are independent of all other int_mskx bits. if an int_mskx bit is set, the interrupt source associated with that mask bit may generate an interrupt that becomes a pending interrupt. the enable software interrupt (enswint) bit in int_msk3[7] de termines the way an individual bit value written to an int_clrx register is interpreted. when is cleared, writing 1's to an int_ clrx register has no effect. however, writing 0's to an int_clr x register, when enswint is cleared causes the corresponding interrupt to cl ear. if the enswint bit is set, any 0's written to the int_clrx registers are ignored. however, 1's written to an int_clrx regi ster, while enswint is set, caus e an interrupt to post for the corresponding interrupt. software interrupts can aid in debugging interrupt service routines by eliminating the need to create system level interactions that are sometimes necessary to create a hardware-only interrupt. table 69. interrupt clear 0 (int_clr0) [0xda] [r/w] bit # 7 6 5 4 3 2 1 0 field gpio port 1 sleep timer int1 gpio port 0 spi receive spi transmit reserved por/lvd read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 when reading this register: 0 = there is no posted interrupt for the corresponding hardware. 1 = posted interrupt for the corresponding hardware present. writing a ?0? to the bits clears the posted interrupts for the co rresponding hardware. writing a ?1? to the bits and to the ens wint (bit 7 of the int_msk3 register) posts the corresponding hardware interrupt. the gpio interrupts are edge-triggered. table 70. interrupt clear 1 (int_clr1) [0xdb] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved prog interval timer 1 ms program- mable interrupt reserved read/write ? r/w r/w ? ?? ? ? default 0 0 0 0 00 0 0 when reading this register: 0 = there is no posted interrupt for the corresponding hardware. 1 = posted interrupt for the corresponding hardware present. writing a ?0? to the bits clears the posted interrupts for the co rresponding hardware. writing a ?1? to the bits and to the ens wint. bit 7 reserved table 71. interrupt clear 2 (int_clr2) [0xdc] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved reserved reserved gpio port2 reserved int2 16-bit counter wrap reserved read/write ? ? ? r/w ?r/w r/w ? default 0 0 0 0 00 0 0 when reading this register: 0 = there is no posted interrupt for the corresponding hardware 1 = posted interrupt for the corresponding hardware present. writing a ?0? to the bits clears the posted interrupts for the corresponding hardware. writing a ?1? to the bits and to the ens wint (bit 7 of the int_msk3 register) posts the corresponding hardware interrupt. bits 7,6,5,3,0]reserved cyrf69103 document number: 001-07611 rev *i page 54 of 72 table 72. interrupt mask 3 (int_msk3) [0xde] [r/w] bit # 7 6 5 4 3 2 1 0 field enswint reserved read/write r ? ? ? ? ? ? ? default 0 0 0 0 00 0 0 bit 7 enable software interrupt (enswint) 0 = disable. writing 0's to an int_clrx register, when enswint is cleared, cause the corresponding interrupt to clear 1 = enable. writing 1's to an int_clrx register, when enswint is set, cause the corresponding interrupt to post bits 6:0 reserved table 73. interrupt mask 2 (int_msk2) [0xdf] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved reserved reserved gpio port 2 int enable reserved int2 int enable 16-bit counter wrap int enable reserved read/write ? ? ? r/w ?r/w r/w ? default 0 0 0 0 00 0 0 bit 7: reserved bit 6: reserved bit 5: reserved bit 4: gpio port 2 interrupt enable 0 = mask gpio port 2 interrupt 1 = unmask gpio port 2 interrupt bit 3: reserved bit 2: int2 interrupt enable 0 = mask int2 interrupt 1 = unmask int2 interrupt bit 1: 16-bit counter wrap interrupt enable 0 = mask 16-bit counter wrap interrupt 1 = unmask 16-bit counter wrap interrupt bit 0: reserved the gpio interrupts are edge-triggered. cyrf69103 document number: 001-07611 rev *i page 55 of 72 table 74. interrupt mask 1 (int_msk1) [0xe1] [r/w] bit # 7 6 5 4 3 2 1 0 field reserved prog interval timer int enable 1 ms timer int enable reserved read/write r/w r/w r/w ? ?? ? ? default 0 0 0 0 00 0 0 bit 7 reserved bit 6 prog interval timer interrupt enable 0 = mask prog interval timer interrupt 1 = unmask prog interval timer interrupt bit 5 1 ms timer interrupt enable 0 = mask 1 ms interrupt 1 = unmask 1 ms interrupt bit 4:0 reserved table 75. interrupt mask 0 (int_msk0) [0xe0] [r/w] bit # 7 6 5 4 3 2 1 0 field gpio port 1 int enable sleep timer int enable int1 int enable gpio port 0 int enable spi receive int enable spi transmit int enable reserved por/lvd int enable read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 bit 7 gpio port 1 interrupt enable 0 = mask gpio port 1 interrupt 1 = unmask gpio port 1 interrupt bit 6 sleep timer interrupt enable 0 = mask sleep timer interrupt 1 = unmask sleep timer interrupt bit 5 int1 interrupt enable 0 = mask int1 interrupt 1 = unmask int1 interrupt bit 4 gpio port 0 interrupt enable 0 = mask gpio port 0 interrupt 1 = unmask gpio port 0 interrupt bit 3 spi receive interrupt enable 0 = mask spi receive interrupt 1 = unmask spi receive interrupt bit 2 spi transmit enable 0 = mask spi transmit interrupt 1 = unmask spi transmit interrupt bit 1 reserved bit 0 por/lvd interrupt enable 0 = mask por/lvd interrupt 1 = unmask por/lvd interrupt cyrf69103 document number: 001-07611 rev *i page 56 of 72 interrupt vector clear register table 76. interrupt vector clear register (int_vc) [0xe2] [r/w] bit # 7 6 5 4 3 2 1 0 field pending interrupt [7:0] read/write r/w r/w r/w r/w r/w r/w r/w r/w default 0 0 0 0 00 0 0 the interrupt vector clear register (int_vc) holds the interrupt vector for the highest priority pending interrupt when read, and when written clears all pending interrupts. bits 7:0 pending interrupt [7:0] 8-bit data value holds the interrupt vector for the highest priori ty pending interrupt. writing to this register clears all pen ding interrupts. microcontroller function register summary addr name 7 6 5 4 3 2 1 0 r/w default 00 p0data p0.7 reserved reserved p0.4/int2 p0.3/int1 reserved p0.1 reserved b--bb-b- 00000000 01 p1data p1.7 p1.6/smiso p1.5/smosi p1.4/sclk p1.3/ssel p1.2 p1.1 p1.0 bbbbbbb- 00000000 02 p2data reserved p2.1?p2.0 ------bb 00000000 06 p01cr reserved int enable int act low ttl thresh high sink open drain pull up enable output enable bbbbbbbb 00000000 08?09 p03cr? p04cr reserved int act low ttl thresh reserved open drain pull up enable output enable --bb-bbb 00000000 0c p07cr reserved int enable int act low ttl thresh reserved open drain pull up enable output enable -bbb-bbb 00000000 0d p10cr reserved int enable int act low reserved 5k pullup enable output enable bbb----b 00000000 0e p11cr reserved int enable int act low reserved open drain reserved output enable -bb--b-b 00000000 0f p12cr clk output int enable int act low ttl threshold reserved open drain pull up enable output enable bbbb-bbb 00000000 10 p13cr reserved int enable int act low reserved high sink open drain pull up enable output enable -bb-bbbb 00000000 11?13 p14cr? p16cr spi use int enable int act low reserved high sink open drain pull up enable output enable bbb-bbbb 00000000 14 p17cr reserved int enable int act low reserved high sink open drain pull up enable output enable -bb-bbbb 00000000 15 p2cr reserved int enable int act low ttl thresh high sink open drain pull up enable output enable -bbbbbbb 00000000 20 frtmrl free running timer [7:0] bbbbbbbb 00000000 21 frtmrh free running timer [15:8] bbbbbbbb 00000000 26 pitmrl prog interval timer [7:0] rrrrrrrr 00000000 27 pitmrh reserved prog interval timer [11:8] ----rrrr 00000000 28 pirl prog interval [7:0] bbbbbbbb 00000000 29 pirh reserved prog interval [11:8] ----rrrr 00000000 30 cpuclkcr reserved -------- 00000000 31 tmrclkcr tcapclk divider tcapclk select itmrclk divider itmrclk select bbbbbbbb 10001111 34 iosctr foffset[2:0] gain[4:0] bbbbbbbb 000ddddd 36 lposctr 32 khz low power reserved 32 khz bias trim [1:0] 32 khz freq trim [3:0] 0-bbbbbb d-dddddd 3c spidata spidata[7:0] bbbbbbbb 00000000 3d spicr swap lsb first comm mode cpol cpha sclk select bbbbbbbb 00000000 da int_clr0 gpio port 1 sleep timer int1 gpio port 0 spi receive spi transmit reserved por/lvd bbbbbb-b 00000000 db int_clr1 reserved prog interval timer 1 ms timer reserved -bb----- 00000000 dc int_clr2 reserved reserved reserved gpio port 2 reserved int2 16-bit counter wrap reserved ---b-bb- 00000000 cyrf69103 document number: 001-07611 rev *i page 57 of 72 de int_msk3 enswint reserved r------- 00000000 df int_msk2 reserved reserved reserved gpio port 2 int enable reserved int2 int enable 16-bit counter wrap int enable reserved ---b-bb- 00000000 e0 int_msk0 gpio port 1 int enable sleep timer int enable int1 int enable gpio port 0 int enable spi receive int enable spi transmit int enable reserved por/lvd int enable bbbbbb-b 00000000 e1 int_msk1 reserved prog interval timer int enable 1 ms timer int enable reserved -bb----- 00000000 e2 int_vc pending interrupt [7:0] bbbbbbbb 00000000 e3 reswdt reset watchdog timer [7:0] wwwwwww w 00000000 -- cpu_a temporary register t1 [7:0] -------- 00000000 -- cpu_x x[7:0] -------- 00000000 -- cpu_pcl program counter [7:0] -------- 00000000 -- cpu_pch program counter [15:8] -------- 00000000 -- cpu_sp stack pointer [7:0] -------- 00000000 f7 cpu_f reserved xio super carry zero global ie ---brbbb 00000010 ff cpu_scr gies reserved wdrs pors sleep r eserved reserved stop r-ccb--b 00010100 1e0 osc_cr0 reserved no buzz sleep timer [1:0] cpu speed [2:0] --bbbbbb 00001000 1e3 lvdcr reserved porlev[1:0] reserved vm[2:0] --bb-bbb 00000000 1e4 vltcmp reserved lvd ppor ------rr 00000000 1eb eco_tr sleep duty cycle [1:0] reserved bb------ 00000000 microcontroller function register summary (continued) addr name 7 6 5 4 3 2 1 0 r/w default cyrf69103 document number: 001-07611 rev *i page 58 of 72 radio function re gister summary all registers are read and writable, except wh ere noted. registers may be written to or read from either individually or in seq uential groups. a single-byte read or write reads or writes from the addressed register. in crementing burst read and write is a sequenc e that begins with an address, and then reads or wr ites to/from each register in address order for as long as clocking continues. it i s possible to repeatedly read (poll) a single regist er using a nonincrementing burst read. address mnemonic b7 b6 b5 b4 b3 b2 b1 b0 default [4] access [4] 0x00 channel_adr not used channel -1001000 -bbbbbbb 0x01 tx_length_adr tx length 00000000 bbbbbbbb 0x02 tx_ctrl_adr tx go tx clr txb15 irqen txb8 irqen txb0 irqen txberr irqen txc irqen txe irqen 00000011 bbbbbbbb 0x03 tx_cfg_adr not used not used data code length data mode pa setting --000101 --bbbbbb 0x04 tx_irq_status_adr os irq lv irq txb15 irq txb8 irq txb0 irq txberr irq txc irq txe irq -------- rrrrrrrr 0x05 rx_ctrl_adr rx go rsvd rxb16 irqen rxb8 irqen rxb1 irqen rxberr irqen rxc irqen rxe irqen 00000111 bbbbbbbb 0x06 rx_cfg_adr agc en lna att hilo fast turn en not used rxow en vld en 10010-10 bbbbb-bb 0x07 rx_irq_status_adr rxow irq sopdet irq rxb16 irq rxb8 irq rxb1 irq rxberr irq rxc irq rxe irq -------- brrrrrrr 0x08 rx_status_adr rx ack pkt err eop err crc0 bad crc rx code rx data mode -------- rrrrrrrr 0x09 rx_count_adr rx count 00000000 rrrrrrrr 0x0a rx_length_adr rx length 00000000 rrrrrrrr 0x0b pwr_ctrl_adr pmu en lvirq en pmu mode force pfet disable [10.] lvi th pmu outv 10100000 bbb-bbbb 0x0c xtal_ctrl_adr xout fn xsirq en no t used not used freq 000--100 bbb--bbb 0x0d io_cfg_adr irq od irq pol miso od xout od pact l od pactl gpio spi 3pin irq gpio 00000000 bbbbbbbb 0x0e gpio_ctrl_adr xout op miso op pactl op irq op xout ip miso ip pactl ip irq ip 0000---- bbbbrrrr 0x0f xact_cfg_adr ack en not used frc end end state ack to 1-000000 b-bbbbbb 0x10 framing_cfg_adr sop en sop len len en sop th 10100101 bbbbbbbb 0x11 data32_thold_adr not used not used not used not used th32 ----0100 ----bbbb 0x12 data64_thold_adr not used not used not used th64 ---01010 ---bbbbb 0x13 rssi_adr sop not used lna rssi 0-100000 r-rrrrrr 0x14 eop_ctrl_adr [9.] hen hint eop 10100100 bbbbbbbb 0x15 crc_seed_lsb_adr crc seed lsb 00000000 bbbbbbbb 0x16 crc_seed_msb_adr crc seed msb 00000000 bbbbbbbb 0x17 tx_crc_lsb_adr crc lsb -------- rrrrrrrr 0x18 tx_crc_msb_adr crc msb -------- rrrrrrrr 0x19 rx_crc_lsb_adr crc lsb 11111111 rrrrrrrr 0x1a rx_crc_msb_adr crc msb 11111111 rrrrrrrr 0x1b tx_offset_lsb_adr strim lsb 00000000 bbbbbbbb 0x1c tx_offset_msb_adr not used not used not used not used strim msb ----0000 ----bbbb 0x1d mode_override_adr rsvd rsvd frc sen frc awake not used not used rst 00000--0 wwwww--w 0x1e rx_override_adr ack rx rxtx dly man rxack frc rxdr dis crc0 dis rxcrc ace not used 0000000- bbbbbbb- 0x1f tx_override_adr ack tx frc pre rsvd man txack ovrd ack dis txcrc rsvd tx inv 00000000 bbbbbbbb 0x26 xtal_cfg_adr rsvd rsvd rsvd rsvd start dly rsvd rsvd rsvd 00000000 wwwwwww w 0x27 clk_override_adr rsvd rsvd rsvd rsvd rsvd rsvd rxf rsvd 00000000 wwwwwww w 0x28 clk_en_adr rsvd rsvd rsvd rsvd rsvd rsvd rxf rsvd 00000000 wwwwwww w 0x29 rx_abort_adr rsvd rsvd abort en rsvd rsvd rsvd rsvd rsvd 00000000 wwwwwww w 0x32 auto_cal_time_adr auto_cal_time 00000011 wwwwwww w 0x35 auto_cal_offset_adr auto_cal_offset 00000000 wwwwwww w 0x39 analog_ctrl_adr rsvd rsvd rsvd rsvd rsvd rsvd rx inv all slow 00000000 wwwwwww w register files 0x20 tx_buffer_adr tx buffer file -------- wwwwwww w 0x21 rx_buffer_adr rx buffer file -------- rrrrrrrr 0x22 sop_code_adr sop code file note [5] bbbbbbbb 0x23 data_code_adr data code file note [6] bbbbbbbb 0x24 preamble_adr preamble file note [7] bbbbbbbb 0x25 mfg_id_adr mfg id file na rrrrrrrr notes 4. b = read/write; r = read only; w = write only; ?-? = not used, default value is undefined. 5. sop_code_adr default = 0x17ff9e213690c782. 6. data_code_adr default = 0x02f9939702fa5ce3012bf1db0132be6f. 7. preamble_adr default = 0x333302;the count value must be great than 4 for ddr and greater than 8 for sdr 8. registers must be configured or accessed only when the radio is in idle or sleep mode.the pmu, gpios, rssi registers can be a ccessed in active tx and rx mode. 9. eop_ctrl_adr[6:4] must never have the value of ?000? i.e. eop hint symbol count must never be ?0? cyrf69103 document number: 001-07611 rev *i page 59 of 72 absolute maximum ratings exceeding maximum ratings may shorten the useful life of the device. user guidelines are not tested. storage temperature ................................. ?40 c to +90 c ambient temperature with power applied ..... 0 c to +70 c supply voltage on any power supply pin relative to v ss ..............................................?0.3 v to +3.9 v dc voltage to logic inputs [11] ............ ?0.3 v to v io + 0.3 v dc voltage applied to outputs in high z state ..................................... ?0.3 v to v io + 0.3 v static discharge voltage (digital) [12] ...................... >2000 v static discharge voltage (rf) [12] .............................. 1100 v latch up current .....................................+200 ma, ?200 ma ground voltage ................................................................ 0 v f osc (crystal frequency) .......................... 12 mhz 30 ppm dc characteristics (t = 25 ? c) parameter description conditions min typ max unit v bat battery voltage 0?70 ? c 1.8 ? 3.6 v v reg [13] pmu output voltage 2.7v mode 2.7 2.73 ? v v lvd low voltage detect lvdcr [2:0] set to 000 2.69 2.7 2.72 v lvdcr [2:0] set to 001 2.90 2.92 2.94 v lvdcr [2:0] set to 010 3.00 3.02 3.04 v lvdcr [2:0] set to 011 3.10 3.13 3.15 v v io v io voltage 1.8 ? 3.6 v v cc v cc voltage 0?70 ? c 2.4 ? 3.6 v device current (for total current consumption in different modes, for ex ample radio, active, mcu, and sleep, add radio function current and mcu function current) i cc (gfsk) [14] average i cc , 1 mbps, slow channel pa = 5, 2-way, 4 bytes/10 ms cpu speed = 6 mhz ? 9.87 ? ma i cc (32-8dr) [14] average i cc , 250 kbps, fast channel pa = 5, 2-way, 4 bytes/10 ms cpu speed = 6 mhz ? 10.2 ? ma i sb1 sleep mode i cc v cc = 3.0v, mcu sleep, pmu disabled ? 2.72 ? a i sb2 sleep mode i cc v cc = 3.0v, mcu sleep, pmu enabled ? 30.4 ? a notes 11. it is permissible to connect voltages above v io to inputs through a series resistor limiting i nput current to 1 ma. ac timing not guaranteed. 12. human body model (hbm). 13. v reg depends on battery input voltage. 14. includes current drawn while starting crystal, starting syn thesizer, transmitting packet (including sop and crc16), changing to receive mode, and receiving ack handshake. device is in sleep except during this transaction. cyrf69103 document number: 001-07611 rev *i page 60 of 72 radio function currents (v cc = 3.0 v, mcu sleep) idle i cc radio off, xtal active xout disabled ? 1.1 ? ma i synth i cc during synth start ? 8.6 ? ma tx i cc i cc during transmit pa = 5 (?5 dbm) ? 21.2 ? ma tx i cc i cc during transmit pa = 6 (0 dbm) ? 28.5 ? ma tx i cc i cc during transmit pa = 7 (+4 dbm) ? 39.9 ? ma rx i cc i cc during receive lna off, att on. ? 18.9 ? ma rx i cc i cc during receive lna on, att off. ? 21.9 ? ma boost eff pmu boost converter efficiency v bat = 2.5v, v reg = 2.73v, i load = 20 ma ? 83 ? % i load_ext [15] average pmu external load current v bat = 1.8v, v reg = 2.73v, rx mode ? ? 15 ma mcu function currents (v dd = 3.0v) i dd1 v dd operating supply current cpu speed = 6 mhz ? 5.0 ? ma i dd1 v dd operating supply current cpu speed = 3 mhz ? 4.4 ? ma radio function gpio interface v oh1 output high voltage condition 1 at i oh = ?100.0 a v io ? 0.1 v io ? v v oh2 output high voltage condition 2 at i oh = ?2.0 ma v io ? 0.4 v io ? v v ol output low voltage at i ol = 2.0 ma ? 0 0.4 v v ih input high voltage 0.76v io ? v io v v il input low voltage 0 ? 0.24v io v i il input leakage current 0 < v in < v io ?1 0.26 +1 a c in pin input capacitance except xtal, rf n , rf p , rf bias ? 3.5 10 pf mcu function gpio interface r up pull up resistance 4 ? 12 k ? v icr input threshold voltage low, cmos mode low to high edge 40% ? 65% v cc v icf input threshold voltage low, cmos mode high to low edge 30% ? 55% v cc v hc input hysteresis voltage, cmos mode high to low edge 3% ? 10% v cc v ilttl input low voltage, ttl mode ? ? 0.72 v v ihttl input high voltage, ttl mode 1.6 ? ? v v ol1 output low voltage, high drive [16] i ol1 = 50 ma ? ? 1.4 v v ol2 output low voltage, high drive [16] i ol1 = 25 ma ? ? 0.4 v v ol3 output low voltage, low drive i ol2 = 8 ma ? ? 0.8 v v oh output high voltage [17] i oh = 2 ma v cc ? 0.5 ? ? v dc characteristics (continued) (t = 25 ? c) parameter description conditions min typ max unit notes 15. i load_ext is dependant on external components and this entry applies when the components connected to l/d are ss12 series diode and dh53 100lc inductor from sumida. 16. available only on p1.3,p1.4,p1.5,p1.6,p1.7. 17. except for pins p1.0, p1,1 in gpio mode. cyrf69103 document number: 001-07611 rev *i page 61 of 72 figure 19. clock timing ac characteristics parameter description conditions min typ max unit gpio timing t r_gpio output rise time measured between 10 and 90% vdd/vreg with 50 pf load ??50ns t f_gpio output fall time measured between 10 and 90% vdd/vreg with 50 pf load ??15ns f imo internal main oscillator frequency with proper trim values loaded [5] 18.72 ? 26.4 mhz f ilo internal low power oscillator with proper trim values loaded [5] 15.0001 ? 50.0 khz spi timing t smck spi master clock rate f cpuclk /6 ? ? 2 mhz t ssck spi slave clock rate ? ? 2.2 mhz t sckh spi clock high time high for cpol = 0, low for cpol = 1 125 ? ? ns t sckl spi clock low time low for cpol = 0, high for cpol = 1 125 ? ? ns t mdo master data output time [18] sck to data valid ?25 ? 50 ns t mdo1 master data output time, first bit with cpha = 0 time before leading sck edge 100 ? ? ns t msu master input data setup time 50 ? ? ns t mhd master input data hold time 50 ? ? ns t ssu slave input data setup time 50 ? ? ns t shd slave input data hold time 50 ? ? ns t sdo slave data output time sck to data valid ? ? 100 ns t sdo1 slave data output time, first bit with cpha = 0 time after ss low to data valid ? ? 100 ns t sss slave select setup time before first sck edge 150 ? ? ns t ssh slave select hold time after last sck edge 150 ? ? ns clock t cyc t cl t ch note 18. in master mode first bit is available 0.5 spiclk cycle before master clock edge available on the sclk pin. cyrf69103 document number: 001-07611 rev *i page 62 of 72 figure 20. gpio timing diagram figure 21. spi master timing, cpha = 1 10% t r_gpio t f_gpio gpio pin output voltage 90% msb t msu lsb t mhd t sckh t mdo ss sck (cpol=0) sck (cpol=1) mosi miso (ss is under firmware control in spi master mode) t sckl msb lsb cyrf69103 document number: 001-07611 rev *i page 63 of 72 figure 22. spi slave timing, cpha = 1 figure 23. spi master timing, cpha = 0 msb t ssu lsb t shd t sckh t sdo ss sck (cpol=0) sck (cpol=1) mosi miso t sckl t sss t ssh msb lsb msb t msu lsb t mhd t sckh t mdo1 ss sck (cpol=0) sck (cpol=1) mosi miso (ss is under firmware control in spi master mode) t sckl t mdo lsb msb cyrf69103 document number: 001-07611 rev *i page 64 of 72 figure 24. spi slave timing, cpha = 0 msb t ssu lsb t shd t sckh t sdo1 ss sck (cpol=0) sck (cpol=1) mosi miso t sckl t sdo lsb msb t sss t ssh cyrf69103 document number: 001-07611 rev *i page 65 of 72 rf characteristics table 77. radio parameters parameter description conditions min typ max unit rf frequency range subject to regulation 2.400 ? 2.497 ghz receiver (t = 25 c, v cc = 3.0 v, f osc = 12.000 mhz, ber < 10 ? 3 ) sensitivity 125 kbps 64-8dr ber 1e-3 ? ?97 ? dbm sensitivity 250 kbps 32-8dr ber 1e-3 ? ?93 ? dbm sensitivity cer 1e-3 ?80 ?87 ? dbm sensitivity gfsk ber 1e-3, all slow = 1 ? ?84 ? dbm lna gain ? 22.8 ? db att gain ? ?31.7 ? db maximum received signal lna on ?15 ?6 ? dbm rssi value for pwr in ?60 dbm [19] lna on ?21?count rssi slope ? 1.9 ? db/count interference performance (cer 1e-3) co-channel interference rejection carrier-to-interf erence (c/i) c = ?60 dbm, ? 9 ? db adjacent (1 mhz) channel selectivity c/i 1 mhz c = ?60 dbm ? 3 ? db adjacent (2 mhz) channel selectivity c/i 2 mhz c = ?60 dbm ? ?30 ? db adjacent (> 3 mhz) channel selectivity c/i > 3 mhz c = ?67 dbm ? ?38 ? db out-of-band blocking 30 mhz?12.75 mhz [20] c = ?67 dbm ? ?30 ? dbm intermodulation c = ?64 dbm, ? f = 5,10 mhz ? ?36 ? dbm receive spurious emission 800 mhz 100 khz resbw ? ?79 ? dbm 1.6 ghz 100 khz resbw ? ?71 ? dbm 3.2 ghz 100 khz resbw ? ?65 ? dbm transmitter (t = 25c, v cc = 3.0v, f osc = 12.000 mhz) maximum rf transmit power pa = 7 +2 4 +6 dbm maximum rf transmit power pa = 6 ?2 0 +2 dbm maximum rf transmit power pa = 5 ?7 ?5 ?3 dbm maximum rf transmit power pa = 0 ? ?35 ? dbm rf power control range ? 39 ? db rf power range control step size seven steps, monotonic ? 5.6 ? db frequency deviation min pn code pattern 10101010 ? 270 ? khz frequency deviation max pn code pattern 11110000 ? 323 ? khz error vector magnitude (fsk error) >0 dbm ? 10 ? %rms occupied bandwidth ?6 dbc, 100 khz resbw 500 876 ? khz notes 19. rssi value is not guaranteed. extensive variation from part to part. 20. exceptions f/3 & 5c/3. cyrf69103 document number: 001-07611 rev *i page 66 of 72 transmit spurious emission (pa = 7) in-band spurious second channel power (2 mhz) ? ?38 ? dbm in-band spurious third channel power (> 3 mhz) ? ?44 ? dbm non-harmonically related spurs (8.000 ghz) ? ?38 ? dbm non-harmonically related spurs (1.6 ghz) ? ?34 ? dbm non-harmonically related spurs (3.2 ghz) ? ?47 ? dbm harmonic spurs (second harmonic) ? ?43 ? dbm harmonic spurs (third harmonic) ? ?48 ? dbm fourth and greater harmonics ? ?59 ? dbm power management (crystal pn# ecera gf-1200008) crystal start to 10ppm ? 0.7 1.3 ms crystal start to irq xsirq en = 1 ? 0.6 ? ms synth settle slow channels ? ? 270 s synth settle medium channels ? ? 180 s synth settle fast channels ? ? 100 s link turnaround time gfsk ? ? 30 s link turnaround time 250 kbps ? ? 62 s link turnaround time 125 kbps ? ? 94 s link turnaround time <125 kbps ? ? 31 s max. packet length < 60 ppm crystal-to-crystal all modes except 64-ddr and 64-sdr ? ? 40 bytes max. packet length < 60 ppm crystal-to-crystal 64-ddr and 64-sdr ? ? 16 bytes table 77. radio parameters (continued) parameter description conditions min typ max unit cyrf69103 document number: 001-07611 rev *i page 67 of 72 ordering code definitions ordering information package ordering part number status 40-pin pb-free qfn 6 6 mm (sawn) CYRF69103-40LTXC in production 40-pin pb-free qfn 6 6 mm (punch) cyrf69103-40lfxc nrnd temperature range: c = commercial pb-free package type: lx = lf or lt lf = qfn (punch type); lt = qfn (sawn type) no of pins in package: 40-pin part number marketing code: rf = wireless (radio frequency) product line company id: cy = cypress cy 69103 - 40 x rf c lx cyrf69103 document number: 001-07611 rev *i page 68 of 72 package handling some ic packages require baking before they are soldered onto a pcb to remove moisture that may have been absorbed after leavin g the factory. a label on the packaging has details about actual bake temperature and the minimum bake time to remove this moisture.the maximum bake time is the aggregate time that the pa rts are exposed to the bake temperature. exceeding this exposur e time may degrade device reliability. package diagram figure 25. 40-pin qfn (6 6 1.0 mm) lt40b 3. 50 3.50 e-pad (sawn) p ackage outline, 001-13190 table 78. package handling parameter description min typ max unit t baketemp bake temperature 125 see package label c t baketime bake time see package label 72 hours 001-13190 *h cyrf69103 document number: 001-07611 rev *i page 69 of 72 figure 26. 40-pin qfn (6 6 1.0 mm) lf40a/ly40a (3 .50 3.50 mm) e-pad (punch) package outline, 001-12917 [21] pad exposed solderable 001-12917 *c note 21. not recommended for new design. cyrf69103 document number: 001-07611 rev *i page 70 of 72 acronyms document conventions units of measure table 79. acronyms used in this document acronym description ack acknowledge (packet received, no errors) agc automatic gain control ats auto transaction sequencer cmos complementary metal oxide semiconductor cpu central processing unit eeprom electrically erasable programmable read-only memory gfsk gaussian frequency-shift keying gpio general purpose input/output hid human interface devices i/o input/output ism industrial, scientific, and medical lna low noise amplifier mcu microcontroller unit mosi master out slave in pmu power management unit psoc programmable system-on-chip qfn quad flat no-lead ram random access memory rssi received signal strength indication sck serial clock spi serial peripheral interface srom supervisory read only memory ss slave select ttl transistor-transistor logic table 80. units of measure symbol unit of measure c degree celsius db decibel dbm decibel-milliwatt ghz gigahertz hz hertz khz kilohertz k ? kilohm mhz megahertz ? f microfarad ? s microsecond ? w microwatt ma milliampere mm millimeter ms millisecond mv millivolt ns nanosecond ? ohm % percent ppm parts per million pf picofarad v volt cyrf69103 document number: 001-07611 rev *i page 71 of 72 document history page document title: cyrf69103, programmable radio on chip low power document #: 001-07611 rev. ecn no. orig. of change submission date description of change ** 479801 oyr see ecn new advance data sheet. *a 501282 oyr see ecn preliminary data sheet. created preliminary data shee t from advance information. *b 631696 boo see ecn final data sheet. updated dc characteristics table with characterization data. minor text changes gpio capacitance and timing diagram included sleep and wakeup sequence documented pit timer registers? r/w cap ability corrected to read only updated radio function register descriptions changed l/d pin description changed rst capacitor from 0.1 uf to 0.47 uf added example pmu configuration circuits *c 2447906 aesa see ecn upda ted to new template *d 2615458 kku / aesa 01/13/2009 replaced 51-85190 with 001-12917. fixed format and language inconsis- tencies. *e 2761532 dvja 09/09/2009 changed default value of the sleep timer from 00(512 hz) to 01(64 hz) in the osc_cr0 [0x1e0] register. *f 2885149 kku 02/26/2010 updated the following sections: microcontroller function , clock architectu re description , cpu clock during sleep mode , sleep mode , low power in sleep mode , general purpose i/o ports , microcontroller function register summary , and package diagram *g 3552304 antg 03/15/2012 added sub-section receive spurious response under the main section functional block overview . updated rf characteristics (updated table 77 (added note 19 and referred the same note in the parameter ?rssi value for pwr in ?60 dbm?)). added ordering code definitions . updated package diagram (added figure 25 ). added acronyms and units of measure . *h 3717153 ankc 08/21/2012 updated ordering information (no change in part numbers, included a column ?status?). updated package diagram (spec 001-13190 (changed revision from *g to *h), added note 21 and referred the same note in figure 26 ). *i 3913209 ankc 02/25/2013 updated pinouts (updated figure 1 ). updated pin definitions (updated descriptions of pin 21 and pin 22). updated functional block overview (updated 2.4 ghz radio (replaced seven steps with eight steps)). updated general purpose i/o ports (updated gpio port configuration (updated high sink (removed cy7c601xx, cy7c602xx related information), updated spi use (removed cy7c601xx, cy7c6 02xx related information))). document number: 001-07611 rev *i revised february 25, 2013 page 72 of 72 wirelessusb, psoc, encore and proc are trademarks of cypress semiconductor corporation. all products and company names mentione d in this document may be the trademarks of their respective holders. cyrf69103 ? cypress semiconductor corporation, 2006-2013. the information contained herein is subject to change without notice. cypress s emiconductor corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a cypress product. nor does it convey or imply any license under patent or other rights. cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement wi th cypress. furthermore, cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. any source code (software and/or firmware) is owned by cypress semiconductor corporation (cypress) and is protected by and subj ect to worldwide patent protection (united states and foreign), united states copyright laws and internatio nal treaty provisions. cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of, and compile the cypress source code and derivative works for the sole purpose of creating custom software and or firmware in su pport of licensee product to be used only in conjunction with a cypress integrated circuit as specified in the applicable agreement. any reproduction, modification, translation, compilation, or repre sentation of this source code except as specified above is prohibited without the express written permission of cypress. disclaimer: cypress makes no warranty of any kind, express or implied, with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. cypress reserves the right to make changes without further notice to t he materials described herein. cypress does not assume any liability arising out of the application or use of any product or circuit described herein. cypress does not authori ze its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress? prod uct in a life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. use may be limited by and subject to the applicable cypress software license agreement. sales, solutions, and legal information worldwide sales and design support cypress maintains a worldwide network of offices, solution center s, manufacturer?s representative s, and distributors. to find t he office closest to you, visit us at cypress locations . products automotive cypress.co m/go/automotive clocks & buffers cypress.com/go/clocks interface cypress. com/go/interface lighting & power control cypress.com/go/powerpsoc cypress.com/go/plc memory cypress.com/go/memory optical & image sensing cypress.com/go/image psoc cypress.com/go/psoc touch sensing cyp ress.com/go/touch usb controllers cypress.com/go/usb wireless/rf cypress.com/go/wireless psoc solutions psoc.cypress.com/solutions psoc 1 | psoc 3 | psoc 5 |
Price & Availability of CYRF69103-40LTXC
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |